#jujutsu — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jujutsu, aggregated by home.social.
-
-
-
-
-
-
TOHO animation and NIJISANJI EN Bring Anime Expo 2026 Home With Shu Yamino & Meloco Kyoran
Shu Yamino and Meloco Kyoran take...
https://comiccrusaders.com/comics/comic-book-previews/toho-animation-and-nijisanji-en-bring-anime-expo-2026-home-with-shu-yamino-meloco-kyoran/
#TOHO animation #NIJISANJI EN #Shu Yamino #Meloco Kyoran #Anime Expo 2026 #Hana Hishikawa #OHIOBOSS SATOYU #My Hero Academia #Jujutsu Kaisen #Frieren #The Apothecary Diaries #Though I Am an Inept Villainess #VTuber #Anime News -
TOHO animation and NIJISANJI EN Bring Anime Expo 2026 Home With Shu Yamino & Meloco Kyoran
Shu Yamino and Meloco Kyoran take...
https://comiccrusaders.com/comics/comic-book-previews/toho-animation-and-nijisanji-en-bring-anime-expo-2026-home-with-shu-yamino-meloco-kyoran/
#TOHO animation #NIJISANJI EN #Shu Yamino #Meloco Kyoran #Anime Expo 2026 #Hana Hishikawa #OHIOBOSS SATOYU #My Hero Academia #Jujutsu Kaisen #Frieren #The Apothecary Diaries #Though I Am an Inept Villainess #VTuber #Anime News -
🚀 JJ-FZF 0.42.0 is out!
⚔️ Alt-L: interactive conflict resolution with jj resolve
🔄 Ctrl-R: rewrite change ID (jj metaedit --update-change-id)
📜 Ctrl-O: keep showing *all* oplog changes (jj-0.40+)
🧠 Cleaner LLM commit message generation
📝 Supports jj describe --editor (jj-0.42)
⏱️ Error pause delays configurable via $JJFZF_ERROR_DELAY
🔧 Fixed bookmark startup position & quoting⚠️ Requires jj-0.42.0, fzf-0.67.0, GNU Make ≥ 4.0, bash ≥ 5.1
🔗 Release:
https://github.com/tim-janik/jj-fzf/releases/tag/v0.42.0 -
🚀 JJ-FZF 0.42.0 is out!
⚔️ Alt-L: interactive conflict resolution with jj resolve
🔄 Ctrl-R: rewrite change ID (jj metaedit --update-change-id)
📜 Ctrl-O: keep showing *all* oplog changes (jj-0.40+)
🧠 Cleaner LLM commit message generation
📝 Supports jj describe --editor (jj-0.42)
⏱️ Error pause delays configurable via $JJFZF_ERROR_DELAY
🔧 Fixed bookmark startup position & quoting⚠️ Requires jj-0.42.0, fzf-0.67.0, GNU Make ≥ 4.0, bash ≥ 5.1
🔗 Release:
https://github.com/tim-janik/jj-fzf/releases/tag/v0.42.0 -
🚀 JJ-FZF 0.42.0 is out!
⚔️ Alt-L: interactive conflict resolution with jj resolve
🔄 Ctrl-R: rewrite change ID (jj metaedit --update-change-id)
📜 Ctrl-O: keep showing *all* oplog changes (jj-0.40+)
🧠 Cleaner LLM commit message generation
📝 Supports jj describe --editor (jj-0.42)
⏱️ Error pause delays configurable via $JJFZF_ERROR_DELAY
🔧 Fixed bookmark startup position & quoting⚠️ Requires jj-0.42.0, fzf-0.67.0, GNU Make ≥ 4.0, bash ≥ 5.1
🔗 Release:
https://github.com/tim-janik/jj-fzf/releases/tag/v0.42.0 -
🚀 JJ-FZF 0.42.0 is out!
⚔️ Alt-L: interactive conflict resolution with jj resolve
🔄 Ctrl-R: rewrite change ID (jj metaedit --update-change-id)
📜 Ctrl-O: keep showing *all* oplog changes (jj-0.40+)
🧠 Cleaner LLM commit message generation
📝 Supports jj describe --editor (jj-0.42)
⏱️ Error pause delays configurable via $JJFZF_ERROR_DELAY
🔧 Fixed bookmark startup position & quoting⚠️ Requires jj-0.42.0, fzf-0.67.0, GNU Make ≥ 4.0, bash ≥ 5.1
🔗 Release:
https://github.com/tim-janik/jj-fzf/releases/tag/v0.42.0 -
🚀 JJ-FZF 0.42.0 is out!
⚔️ Alt-L: interactive conflict resolution with jj resolve
🔄 Ctrl-R: rewrite change ID (jj metaedit --update-change-id)
📜 Ctrl-O: keep showing *all* oplog changes (jj-0.40+)
🧠 Cleaner LLM commit message generation
📝 Supports jj describe --editor (jj-0.42)
⏱️ Error pause delays configurable via $JJFZF_ERROR_DELAY
🔧 Fixed bookmark startup position & quoting⚠️ Requires jj-0.42.0, fzf-0.67.0, GNU Make ≥ 4.0, bash ≥ 5.1
🔗 Release:
https://github.com/tim-janik/jj-fzf/releases/tag/v0.42.0 -
#jujutsu now supports interactive absorb! 😍 You need to be in version >= v0.44. But still. I cannot express how many times I ran into trying to use `-i` on absorb as an error. Now it actually works!! 🥹
https://docs.jj-vcs.dev/latest/changelog/#:~:text=jj%20absorb,commit,-%2E
-
#jujutsu now supports interactive absorb! 😍 You need to be in version >= v0.44. But still. I cannot express how many times I ran into trying to use `-i` on absorb as an error. Now it actually works!! 🥹
https://docs.jj-vcs.dev/latest/changelog/#:~:text=jj%20absorb,commit,-%2E
-
#jujutsu now supports interactive absorb! 😍 You need to be in version >= v0.44. But still. I cannot express how many times I ran into trying to use `-i` on absorb as an error. Now it actually works!! 🥹
https://docs.jj-vcs.dev/latest/changelog/#:~:text=jj%20absorb,commit,-%2E
-
#jujutsu now supports interactive absorb! 😍 You need to be in version >= v0.44. But still. I cannot express how many times I ran into trying to use `-i` on absorb as an error. Now it actually works!! 🥹
https://docs.jj-vcs.dev/latest/changelog/#:~:text=jj%20absorb,commit,-%2E
-
#jujutsu now supports interactive absorb! 😍 You need to be in version >= v0.44. But still. I cannot express how many times I ran into trying to use `-i` on absorb as an error. Now it actually works!! 🥹
https://docs.jj-vcs.dev/latest/changelog/#:~:text=jj%20absorb,commit,-%2E
-
#Jujutsu jest... interesujące. To chyba najlepsze sformułowanie po tym artykule i innych materiałach (polecamy podpytać ChatGPT o różnice względem #Git i Jujutsu) - widać, że to narzędzie proponuje inny sposób pracy na repozytorium i inną filozofię. Warto znać, to na pewno.
https://www.stavros.io/posts/switch-to-jujutsu-already-a-tutorial/
-
#Jujutsu jest... interesujące. To chyba najlepsze sformułowanie po tym artykule i innych materiałach (polecamy podpytać ChatGPT o różnice względem #Git i Jujutsu) - widać, że to narzędzie proponuje inny sposób pracy na repozytorium i inną filozofię. Warto znać, to na pewno.
https://www.stavros.io/posts/switch-to-jujutsu-already-a-tutorial/
-
#Jujutsu jest... interesujące. To chyba najlepsze sformułowanie po tym artykule i innych materiałach (polecamy podpytać ChatGPT o różnice względem #Git i Jujutsu) - widać, że to narzędzie proponuje inny sposób pracy na repozytorium i inną filozofię. Warto znać, to na pewno.
https://www.stavros.io/posts/switch-to-jujutsu-already-a-tutorial/
-
The result that I needed in my #jujutsu config file was this:
I don't want jj to track main/master unless I do so explicitly (
track-default-bookmark-on-clone = false)I don't want jj to automatically track bookmarks at all (don't set
auto-track-bookmarks)I want jj to advance the bookmark as soon as I commit (
experimental-advance-branches)I want jj to only advance the bookmark in my branches (
experimental-advance-branches.enabled-branches = ["glob:work/myname/*"])I don't want jj to ever move the bookmark on main/master unless I do so explicitly (
experimental-advance-branches.disabled-branches = ["main"])in the case I accidentally push a not advanced bookmark, I want jj to have a more readable default autogenerated branch name based on the commit name without spaces and without single quotes in lowercase (
templates.git_push_bookmark = "\"work/myname/\" ++ description.first_line().replace(\" \", \"-\").replace(\"'\", \"\").lower()")
-
The result that I needed in my #jujutsu config file was this:
I don't want jj to track main/master unless I do so explicitly (
track-default-bookmark-on-clone = false)I don't want jj to automatically track bookmarks at all (don't set
auto-track-bookmarks)I want jj to advance the bookmark as soon as I commit (
experimental-advance-branches)I want jj to only advance the bookmark in my branches (
experimental-advance-branches.enabled-branches = ["glob:work/myname/*"])I don't want jj to ever move the bookmark on main/master unless I do so explicitly (
experimental-advance-branches.disabled-branches = ["main"])in the case I accidentally push a not advanced bookmark, I want jj to have a more readable default autogenerated branch name based on the commit name without spaces and without single quotes in lowercase (
templates.git_push_bookmark = "\"work/myname/\" ++ description.first_line().replace(\" \", \"-\").replace(\"'\", \"\").lower()")
-
The result that I needed in my #jujutsu config file was this:
I don't want jj to track main/master unless I do so explicitly (
track-default-bookmark-on-clone = false)I don't want jj to automatically track bookmarks at all (don't set
auto-track-bookmarks)I want jj to advance the bookmark as soon as I commit (
experimental-advance-branches)I want jj to only advance the bookmark in my branches (
experimental-advance-branches.enabled-branches = ["glob:work/myname/*"])I don't want jj to ever move the bookmark on main/master unless I do so explicitly (
experimental-advance-branches.disabled-branches = ["main"])in the case I accidentally push a not advanced bookmark, I want jj to have a more readable default autogenerated branch name based on the commit name without spaces and without single quotes in lowercase (
templates.git_push_bookmark = "\"work/myname/\" ++ description.first_line().replace(\" \", \"-\").replace(\"'\", \"\").lower()")
-
The result that I needed in my #jujutsu config file was this:
I don't want jj to track main/master unless I do so explicitly (
track-default-bookmark-on-clone = false)I don't want jj to automatically track bookmarks at all (don't set
auto-track-bookmarks)I want jj to advance the bookmark as soon as I commit (
experimental-advance-branches)I want jj to only advance the bookmark in my branches (
experimental-advance-branches.enabled-branches = ["glob:work/myname/*"])I don't want jj to ever move the bookmark on main/master unless I do so explicitly (
experimental-advance-branches.disabled-branches = ["main"])in the case I accidentally push a not advanced bookmark, I want jj to have a more readable default autogenerated branch name based on the commit name without spaces and without single quotes in lowercase (
templates.git_push_bookmark = "\"work/myname/\" ++ description.first_line().replace(\" \", \"-\").replace(\"'\", \"\").lower()")
-
I've been trying #jujutsu (jj) for a while. It's an alternative frontend to git, but unlike other tools like lazygit, it actually changes the git workflow.
Essentially:
- there's no index/staging area
- changes are separate from commits
- because of the above two, all changes to files are tracked ("committed to jj") by default (in other words, the current commit is the latest change)
- there's no concept of current branch, you just move/advance the branch pointer (bookmark) to current change
- this also means you work on anonymous commits by default and only track the parent commit
- rebase and squash are actually not fucking miserable
- you can keep working while a rebase is marked as having a conflict
But there's two things I don't like about it:
- it pushes all created tracked branches by default
- you have to move the bookmark before pushing, otherwise pushing creates an autogenerated branch name
For the latter there's an experimental advance branches feature, I haven't investigated the first yet.
-
I've been trying #jujutsu (jj) for a while. It's an alternative frontend to git, but unlike other tools like lazygit, it actually changes the git workflow.
Essentially:
- there's no index/staging area
- changes are separate from commits
- because of the above two, all changes to files are tracked ("committed to jj") by default (in other words, the current commit is the latest change)
- there's no concept of current branch, you just move/advance the branch pointer (bookmark) to current change
- this also means you work on anonymous commits by default and only track the parent commit
- rebase and squash are actually not fucking miserable
- you can keep working while a rebase is marked as having a conflict
But there's two things I don't like about it:
- it pushes all created tracked branches by default
- you have to move the bookmark before pushing, otherwise pushing creates an autogenerated branch name
For the latter there's an experimental advance branches feature, I haven't investigated the first yet.
-
I've been trying #jujutsu (jj) for a while. It's an alternative frontend to git, but unlike other tools like lazygit, it actually changes the git workflow.
Essentially:
- there's no index/staging area
- changes are separate from commits
- because of the above two, all changes to files are tracked ("committed to jj") by default (in other words, the current commit is the latest change)
- there's no concept of current branch, you just move/advance the branch pointer (bookmark) to current change
- this also means you work on anonymous commits by default and only track the parent commit
- rebase and squash are actually not fucking miserable
- you can keep working while a rebase is marked as having a conflict
But there's two things I don't like about it:
- it pushes all created tracked branches by default
- you have to move the bookmark before pushing, otherwise pushing creates an autogenerated branch name
For the latter there's an experimental advance branches feature, I haven't investigated the first yet.
-
I've been trying #jujutsu (jj) for a while. It's an alternative frontend to git, but unlike other tools like lazygit, it actually changes the git workflow.
Essentially:
- there's no index/staging area
- changes are separate from commits
- because of the above two, all changes to files are tracked ("committed to jj") by default (in other words, the current commit is the latest change)
- there's no concept of current branch, you just move/advance the branch pointer (bookmark) to current change
- this also means you work on anonymous commits by default and only track the parent commit
- rebase and squash are actually not fucking miserable
- you can keep working while a rebase is marked as having a conflict
But there's two things I don't like about it:
- it pushes all created tracked branches by default
- you have to move the bookmark before pushing, otherwise pushing creates an autogenerated branch name
For the latter there's an experimental advance branches feature, I haven't investigated the first yet.
-
-
-
-
-
-
I haven’t really gotten the idea of #jujutsu before since I’m pretty happy with git, but the idea of not having to name things (branches, commits) kinda clicks with me so maybe I’ll try and give it a go!
-
I haven’t really gotten the idea of #jujutsu before since I’m pretty happy with git, but the idea of not having to name things (branches, commits) kinda clicks with me so maybe I’ll try and give it a go!
-
I haven’t really gotten the idea of #jujutsu before since I’m pretty happy with git, but the idea of not having to name things (branches, commits) kinda clicks with me so maybe I’ll try and give it a go!
-
I haven’t really gotten the idea of #jujutsu before since I’m pretty happy with git, but the idea of not having to name things (branches, commits) kinda clicks with me so maybe I’ll try and give it a go!
-
I haven’t really gotten the idea of #jujutsu before since I’m pretty happy with git, but the idea of not having to name things (branches, commits) kinda clicks with me so maybe I’ll try and give it a go!
-
RE: https://wandering.shop/@offby1/117048970918039631
This got me thinking it'd be worth writing this down: https://offby1.website/posts/how-i-jujutsu-bookmark-advance.html
tl;dr, this is how I have set up `jj bookmark advance`
-
RE: https://wandering.shop/@offby1/117048970918039631
This got me thinking it'd be worth writing this down: https://offby1.website/posts/how-i-jujutsu-bookmark-advance.html
tl;dr, this is how I have set up `jj bookmark advance`
-
RE: https://wandering.shop/@offby1/117048970918039631
This got me thinking it'd be worth writing this down: https://offby1.website/posts/how-i-jujutsu-bookmark-advance.html
tl;dr, this is how I have set up `jj bookmark advance`
-
RE: https://wandering.shop/@offby1/117048970918039631
This got me thinking it'd be worth writing this down: https://offby1.website/posts/how-i-jujutsu-bookmark-advance.html
tl;dr, this is how I have set up `jj bookmark advance`
-
RE: https://wandering.shop/@offby1/117048970918039631
This got me thinking it'd be worth writing this down: https://offby1.website/posts/how-i-jujutsu-bookmark-advance.html
tl;dr, this is how I have set up `jj bookmark advance`
-
#jujutsu #vcs still lots of fun to use (I've since updated my default tmux session config to stop popping out #git related panes like lazygit) but also still getting my head around best practices and ergonomics.
E.g., `jj bookmark advance` clearly prefers that your head/@ be a "real commit"; if you're sitting on an empty commit after a `jj new` or `jj commit` or etc, you have to remember to say `jj bookmark advance --to @-` which is easy to forget.
Conversely, jj's behavior of "@ contains your working copy as-is, there's no index/staging" means you're incentivized /not/ to be sitting on "real work" lest you accidentally perform the equivalent of `git commit --amend` every time you edit a file. (This bites me a lot! Especially for files that another tool is auto-updating like uv.lock, Pulumi.$env.yml etc.)
-
#jujutsu #vcs still lots of fun to use (I've since updated my default tmux session config to stop popping out #git related panes like lazygit) but also still getting my head around best practices and ergonomics.
E.g., `jj bookmark advance` clearly prefers that your head/@ be a "real commit"; if you're sitting on an empty commit after a `jj new` or `jj commit` or etc, you have to remember to say `jj bookmark advance --to @-` which is easy to forget.
Conversely, jj's behavior of "@ contains your working copy as-is, there's no index/staging" means you're incentivized /not/ to be sitting on "real work" lest you accidentally perform the equivalent of `git commit --amend` every time you edit a file. (This bites me a lot! Especially for files that another tool is auto-updating like uv.lock, Pulumi.$env.yml etc.)
-
#jujutsu #vcs still lots of fun to use (I've since updated my default tmux session config to stop popping out #git related panes like lazygit) but also still getting my head around best practices and ergonomics.
E.g., `jj bookmark advance` clearly prefers that your head/@ be a "real commit"; if you're sitting on an empty commit after a `jj new` or `jj commit` or etc, you have to remember to say `jj bookmark advance --to @-` which is easy to forget.
Conversely, jj's behavior of "@ contains your working copy as-is, there's no index/staging" means you're incentivized /not/ to be sitting on "real work" lest you accidentally perform the equivalent of `git commit --amend` every time you edit a file. (This bites me a lot! Especially for files that another tool is auto-updating like uv.lock, Pulumi.$env.yml etc.)
-
#jujutsu #vcs still lots of fun to use (I've since updated my default tmux session config to stop popping out #git related panes like lazygit) but also still getting my head around best practices and ergonomics.
E.g., `jj bookmark advance` clearly prefers that your head/@ be a "real commit"; if you're sitting on an empty commit after a `jj new` or `jj commit` or etc, you have to remember to say `jj bookmark advance --to @-` which is easy to forget.
Conversely, jj's behavior of "@ contains your working copy as-is, there's no index/staging" means you're incentivized /not/ to be sitting on "real work" lest you accidentally perform the equivalent of `git commit --amend` every time you edit a file. (This bites me a lot! Especially for files that another tool is auto-updating like uv.lock, Pulumi.$env.yml etc.)
-
#jujutsu #vcs still lots of fun to use (I've since updated my default tmux session config to stop popping out #git related panes like lazygit) but also still getting my head around best practices and ergonomics.
E.g., `jj bookmark advance` clearly prefers that your head/@ be a "real commit"; if you're sitting on an empty commit after a `jj new` or `jj commit` or etc, you have to remember to say `jj bookmark advance --to @-` which is easy to forget.
Conversely, jj's behavior of "@ contains your working copy as-is, there's no index/staging" means you're incentivized /not/ to be sitting on "real work" lest you accidentally perform the equivalent of `git commit --amend` every time you edit a file. (This bites me a lot! Especially for files that another tool is auto-updating like uv.lock, Pulumi.$env.yml etc.)
-
🌿 Mirrors Git diff-style commands: hunk diff, hunk show HEAD~1, file-to-file compare and patches from stdin
🔀 Auto-detects #Jujutsu and #Sapling checkouts and uses native revsets; can be set as pager for #Git, jj or sl
🎨 TOML config for theme, layout mode, VCS, line numbers and wrapping, plus custom themes inheriting from any built-in theme
-
🌿 Mirrors Git diff-style commands: hunk diff, hunk show HEAD~1, file-to-file compare and patches from stdin
🔀 Auto-detects #Jujutsu and #Sapling checkouts and uses native revsets; can be set as pager for #Git, jj or sl
🎨 TOML config for theme, layout mode, VCS, line numbers and wrapping, plus custom themes inheriting from any built-in theme
-
🌿 Mirrors Git diff-style commands: hunk diff, hunk show HEAD~1, file-to-file compare and patches from stdin
🔀 Auto-detects #Jujutsu and #Sapling checkouts and uses native revsets; can be set as pager for #Git, jj or sl
🎨 TOML config for theme, layout mode, VCS, line numbers and wrapping, plus custom themes inheriting from any built-in theme
-
🌿 Mirrors Git diff-style commands: hunk diff, hunk show HEAD~1, file-to-file compare and patches from stdin
🔀 Auto-detects #Jujutsu and #Sapling checkouts and uses native revsets; can be set as pager for #Git, jj or sl
🎨 TOML config for theme, layout mode, VCS, line numbers and wrapping, plus custom themes inheriting from any built-in theme
-
🌿 Mirrors Git diff-style commands: hunk diff, hunk show HEAD~1, file-to-file compare and patches from stdin
🔀 Auto-detects #Jujutsu and #Sapling checkouts and uses native revsets; can be set as pager for #Git, jj or sl
🎨 TOML config for theme, layout mode, VCS, line numbers and wrapping, plus custom themes inheriting from any built-in theme
-
#TIL: #jj #jujutsu grew a `bookmark advance` this past spring. Very cross I didn't even know about it until just now, given I only started using it this summer…
https://www.jj-vcs.dev/latest/cli-reference/#jj-bookmark-advance
Now glad I didn't even bother setting up the "usual" 'tug' alias!
-
#TIL: #jj #jujutsu grew a `bookmark advance` this past spring. Very cross I didn't even know about it until just now, given I only started using it this summer…
https://www.jj-vcs.dev/latest/cli-reference/#jj-bookmark-advance
Now glad I didn't even bother setting up the "usual" 'tug' alias!
-
#TIL: #jj #jujutsu grew a `bookmark advance` this past spring. Very cross I didn't even know about it until just now, given I only started using it this summer…
https://www.jj-vcs.dev/latest/cli-reference/#jj-bookmark-advance
Now glad I didn't even bother setting up the "usual" 'tug' alias!
-
#TIL: #jj #jujutsu grew a `bookmark advance` this past spring. Very cross I didn't even know about it until just now, given I only started using it this summer…
https://www.jj-vcs.dev/latest/cli-reference/#jj-bookmark-advance
Now glad I didn't even bother setting up the "usual" 'tug' alias!
-
#TIL: #jj #jujutsu grew a `bookmark advance` this past spring. Very cross I didn't even know about it until just now, given I only started using it this summer…
https://www.jj-vcs.dev/latest/cli-reference/#jj-bookmark-advance
Now glad I didn't even bother setting up the "usual" 'tug' alias!
-
Workflow changes I've made in the past 12 months, and am very happy with:
tmux → zellij
vim → neovim
git → jujutsu
notion → obsidianOf those, #jujutsu is the biggest improvement. If you use `git rebase` or `git stash` regularly, you're probably the kind of person who would love it too.
-
Workflow changes I've made in the past 12 months, and am very happy with:
tmux → zellij
vim → neovim
git → jujutsu
notion → obsidianOf those, #jujutsu is the biggest improvement. If you use `git rebase` or `git stash` regularly, you're probably the kind of person who would love it too.