majutsu a magit inspired Emacs client for jujutsu
majutsu a magit inspired Emacs client for jujutsu
New blog post: "More Jujutsu tricks"
https://schafe-sind-bessere-rasenmaeher.de/tech/more-jujutsu-tricks/
I've learned a lot in the last two weeks and wanted to share it with you. 🙂
I finally realized why I run into stale workspace issue frequently:
JJ will set up a Watchman trigger if it is configured to use Watchman as fsmonitor. The trigger will run `jj debug snapshot` whenever something changes in the repo.
Now, this will clash with any jj command I run and causing a stale workspace.
I think the obvious solution is to disable snapshotting in JJ commands if Watchman trigger is created. However there doesn't seem to be a config option for this. hmm
Jujutsu v0.38.0
https://github.com/jj-vcs/jj/releases/tag/v0.38.0
Release highlights:
- Per-repo and per-workspace config is now stored outside the repo, for security reasons. This is not a breaking change because legacy repos are automatically migrated to this new format. `.jj/repo/config.toml` and `.jj/workspace-config.toml` should no longer be used.
Moving to jj after 20 years of using and advocating for git has been the biggest workflow change I made in recent history.
Git has tons of great concept, but the cli makes the most useful operation painful (ugh... conflicts).
Jujitsu works the way I always wished git would. As simple as that.
I was going to write an article about this, but then I remembered the article that got me started with jj, and it covers everything I would want to cover https://v5.chriskrycho.com/essays/jj-init/
Looks like git is coming for jj's lunch
https://fosdem.org/2026/schedule/event/HTJK33-evolving_git_for_the_next_decade/
OH: IF #jj BANS ME FROM MUTATING OTHERS COMMITS I WILL FACE GOD AND WALK BACKWARDS INTO HELL
' "Git-out-of-the-way source control" is the best tiny description of JJ I've ever seen, because it's both true and the pun works perfectly. '
--https://news.ycombinator.com/item?id=46799435
New blog post: Why I prefer Jujutsu over Git
I've been raving about jj for the last two months and my coworkers have asked multiple times if I could put together a small presentation. I've decided to make it a blog post instead.
https://www.schafe-sind-bessere-rasenmaeher.de/tech/why-i-prefer-jujutsu-over-git/
It's a lot of raving and rambling, but hopefully somebody will get something from it. 😅
#blog #git #jj
(I've learned not to use the "jujutsu" hashtag for this 😅)
I have some thoughts about first week of using jujutsu, including Emacs setup and fixing a non-ideal default option. jj is expecially great for stacked branches and updating main: https://mwolson.org/blog/2026-01-22-first-week-with-jujutsu-vcs/ #jj
@defuneste Maybe jujutsu would help simplify the version control learning curve.
https://www.jj-vcs.dev/latest/
Good guide for people without VC experience https://jj-for-everyone.github.io/
Good guide for people with VC experience https://steveklabnik.github.io/jujutsu-tutorial/
Jujutsu v0.37.0
https://github.com/jj-vcs/jj/releases/tag/v0.37.0
Release highlights:
- A new syntax for referring to hidden and divergent change IDs is available: xyz/n where n is a number. For instance, xyz/0 refers to the latest version of xyz, while xyz/1 refers to the previous version of xyz. This allows you to perform actions like jj restore --from xyz/1 --to xyz to restore xyz to its previous contents, if you made a mistake.
@MoskitoHero it's very annoying to my teammates, I use every opportunity to tell them how great #jj is. Other than that, no problem at all!
Has anyone experience using #JuJutsu as a replacement for #git in the context of an existing team workflow ?
How easy is it to integrate?
#jj
https://github.com/jj-vcs/jj
Today I started looking into #jujutsu. I finally understand what #jj heads are raving about. It's finally *easy* to author the history of code changes.
Editing, splitting and even moving changes in the history is much easier than it used to be with #git. At the same time, it is fully compatible with the ‘old’ world, as it acts as a front end for git.
Marvellous!
The list might grow over the year too😁:
1) Rust
2) Jujutsu VCS
3) Nushell
4) helix motions
5) Nix - much more deeper
6) Pulumi
7) GCP
8) Zellij
9) Tailscale
etc
And more importantly I want to share
my learning journey, findings etc
If u are a fellow learner too of any of these, let's connect😁
Matrix:
https://matrix.to/#/#vivekanandan_ks:matrix.org
#rust #jj #jujutsu #vcs #nushell #vim #vimmotions #helix #nix #pulumi #gcp #cloud #learning #passion #life #newyear2026
@synlogic4242 For me, the killer feature in #JJ is the ability to deal with merge conflicts later. Also, the user interface has fewer concepts, and new commits are really cheap.
On the other hand, for a git repo which you own and where you can just commit whatever without code review, it's not very compelling. JJ shines when you want to continue hacking while you wait for a code review.
If you've ever run `jj jj …` by accident, do I have the alias for you. https://caiustheory.com/jj-jj-jj-jj-jj/ #jj #jujutsu
Inspired by my colleagues at work I'm starting to learn #Jujutsu (jj).
No, not the Japanese martial art, the version control system.
https://www.jj-vcs.dev/latest/
Some things I am looking forward to coming from git:
- no branches
- no index/staging-area
- auto-committed working-copy
- auto-rebased descendant commits
- operation log replacing reflog
Also fully compatible with git, so I can just use it for work while others are still using git.