3 ms·

I love magit and I use it basically every day. But lately, at my work's monorepo, I've been greatly pained by how synchronous it is (like much of Emacs). When I

I love magit and I use it basically every day. But lately, at my work's monorepo, I've been greatly pained by how synchronous it is (like much of Emacs). When I want to fix a unit test, I find suspicious commits by a grep for some keyword through diffs in the git log, and unlike the git CLI, magit will not show me any matching commits until it has searched through all of them (capped at 256 matches by default), which takes a very long time. I love so many creative Emacs tools, but the wait times from magit and consult get painful.

procinct 3y ago
If you’re interested, you should take a look at Sublime Merge. I switched to it a couple of years ago. Made by the creators of Sublime Text so it’s as snappy as you’d expect. And it has some surprisingly powerful tooling when it comes to searching the history (list all commits that changed a file and by a certain author etc). I also like that you can see a log of all of the git commands it’s executing behind the scenes.
- ElectronBadger 3y ago
  I had a brief and rather complicated affair with Emacs some years ago. I tried Magit then. It was ok(ish), but could not understood what all the fuss about. Sublime Merge is so much better -- blazing fast and designed so well. Perhaps I'm not objective here, since I'm also a die-hard fan of Sublime Text -- the best editor for writing research notes, papers, prose, and code :)
dietr1ch 3y ago
At work I go back to using the command line too and use emacs to edit the commit messages. I find it's not only magit that's not ready for huge monorepos. I had to maintain a huge directory blacklist before sparse clones were supported internally (before everything pretended to be around and was streamed/cached underneath, which tripped every regular tool into fetching too much)
TeMPOraL 3y ago
I'm starting to feel the pain too, and we're not even at a monorepo stage - just a large project with lots of history. There's some interference coming from me running Emacs/Magit on WSL1, and corporate nuking my Windows Defender exclusions lists, meaning "real time protection" is slowing every file write down. Still for small to medium repos it's wonderful; for that one large at work, it's... pretty much setting my tea breaks. Currently the most annoying mysterious issue is that some commands (usually pulling or rebasing, sometimes committing too) reach the point of Magit echoing "git finished", and then... whole Emacs remains frozen for 30-120 seconds. I haven't traced that tone to source yet.
- bdzr 3y ago
  > Currently the most annoying mysterious issue is that some commands (usually pulling or rebasing, sometimes committing too) reach the point of Magit echoing "git finished", and then... whole Emacs remains frozen for 30-120 seconds. I haven't traced that tone to source yet. `M-x toggle-debug-on-quit` and `C-g` during the freezing will probably help here, though I would guess the problem is highlighting since that tends to take a lot of time on big diffs.
- ParetoOptimal 3y ago
  > There's some interference coming from me running Emacs/Magit on WSL1, and corporate nuking my Windows Defender exclusions lists In my experience this brings emacs to a crawl.

procinct 3y ago

If you’re interested, you should take a look at Sublime Merge. I switched to it a couple of years ago. Made by the creators of Sublime Text so it’s as snappy as you’d expect. And it has some surprisingly powerful tooling when it comes to searching the history (list all commits that changed a file and by a certain author etc). I also like that you can see a log of all of the git commands it’s executing behind the scenes.

ElectronBadger 3y ago
I had a brief and rather complicated affair with Emacs some years ago. I tried Magit then. It was ok(ish), but could not understood what all the fuss about. Sublime Merge is so much better -- blazing fast and designed so well. Perhaps I'm not objective here, since I'm also a die-hard fan of Sublime Text -- the best editor for writing research notes, papers, prose, and code :)

dietr1ch 3y ago

At work I go back to using the command line too and use emacs to edit the commit messages. I find it's not only magit that's not ready for huge monorepos. I had to maintain a huge directory blacklist before sparse clones were supported internally (before everything pretended to be around and was streamed/cached underneath, which tripped every regular tool into fetching too much)

TeMPOraL 3y ago

I'm starting to feel the pain too, and we're not even at a monorepo stage - just a large project with lots of history. There's some interference coming from me running Emacs/Magit on WSL1, and corporate nuking my Windows Defender exclusions lists, meaning "real time protection" is slowing every file write down. Still for small to medium repos it's wonderful; for that one large at work, it's... pretty much setting my tea breaks. Currently the most annoying mysterious issue is that some commands (usually pulling or rebasing, sometimes committing too) reach the point of Magit echoing "git finished", and then... whole Emacs remains frozen for 30-120 seconds. I haven't traced that tone to source yet.

bdzr 3y ago
> Currently the most annoying mysterious issue is that some commands (usually pulling or rebasing, sometimes committing too) reach the point of Magit echoing "git finished", and then... whole Emacs remains frozen for 30-120 seconds. I haven't traced that tone to source yet. `M-x toggle-debug-on-quit` and `C-g` during the freezing will probably help here, though I would guess the problem is highlighting since that tends to take a lot of time on big diffs.
ParetoOptimal 3y ago
> There's some interference coming from me running Emacs/Magit on WSL1, and corporate nuking my Windows Defender exclusions lists In my experience this brings emacs to a crawl.