In the end, I just stick to Git CLI. It's fast enough, ergonomic enough for the basic usage, and works everywhere. I still wonder people who use multiple IDEs for multiple languages and have to fight different git plugins.
In the end, I just stick to Git CLI. It's fast enough, ergonomic enough for the basic usage, and works everywhere. I still wonder people who use multiple IDEs for multiple languages and have to fight different git plugins.
Edit: found my PR. Give it a try, worked wonders for my magit on windows experience https://github.com/magit/magit/pull/4717
Disappointing that your PR was closed without comment.
If you don't believe windows process spawingin is slow, try this: clone a git repo with 100+ submodules to your windows box. Now enjoy a nice long coffee break anytime you interact with git. And 5 coffee breaks anytime you interact with git via magit.
This should be potentially be solvable by using libgit2 instead of spawning a bunch of processes.
There has been ongoing work to integrate libgit2 into Magit, but I don't know it's current status, nor whether that integration has made it on to Windows yet.
Is it because of slow git process spawning on Windows, or because magit needs multiple git command invocation to perform an action, or is it "only" slow refresh, I don't know. And honestly, I don't care.
It's a chicken and egg problem. It's too slow, so I don't bother to learn it. And since I didn't learn it, I don't see any benefit in using it that could justify hours or even days of digging for performance tweaks and tricks.