Emacs after Magit
5 points by PuercoPop
5 points by PuercoPop
Although my main gripe with Magit is how slow it is one huge repositories like Linux or Servo, what I found most interesting is the shell-command+ package. I mostly use shell-command when running one of commands like bin/rails migrate or bin/rails routes -g. But I might look into using shell-command+ so that commands like bin/rails server routed to shpool automatically instead.
You can usually strip down magit to prevent it from doing expensive operations for those types of repos. This is basically necessary on windows due to the cost of CreateProcess. It usually makes the experience almost just as good as without the extra fanciness.
Nice post, even though I am on the opposite end of the spectrum: I love Magit, and I am also a "gc" (git commit) type of person.
Heck, I even used to abuse "grbi #hash" ("git rebase --interactively #hash") before moving to emacs.
In any case, you might like git toolbelt. It contains a bunch of utilities that could inspire you, such as git spinoff:
https://github.com/nvie/git-toolbelt/commit/6841eff9dd64e0b6a1a22a475a494955968d625a
Initially this was just because Magit added a new dependency cond-let that was conflicting the upstream development of a macro by the same name, but I had already taken issue with the number of dependencies such as llama, and generally do not enjoy Transient-based user interfaces, so I ended up sticking with the descision.
I am also a bit annoyed by this. But not enough to let go of Magit.
Some Git commands require user input, which in a terminal would start a TUI editor like vi or GNU nano. As I am executing commands using M-!, this is an issue, since I am not emulating a proper terminal, and do not intend to do so.
Why not use emacsclient to open the file in the current Emacs instance?