Looking forward to using the new release. "git at the speed of thought" describes magit quite well. Actually sometimes magit nudged me into the direction of looking up some more special git commands, to learn about them and then making use of magit's interface to them, often simply pressing one button more. Magit has not made me forget how command line git works, because it often shows me right there, what the arguments are I am specifying by a few key presses actually are. If it made me forget how to use actual git, I would be thinking: "Meh, but I should know how to use git actually, for the times when I do not have magit around." Fortunately this is not the case at all with magit.
Magit must be one of the best software tools ever written.<p>I sorely missed it when I had to use IntelliJ for a few projects, so I wrote a TUI tool like Magit that can be used inside the console window of most IDEs like IntelliJ etc.<p>Still haven't gotten around to releasing it properly, but it's easy to setup and works well enough to be a working MVP.<p><a href="https://github.com/hugit-project/hugit" rel="nofollow">https://github.com/hugit-project/hugit</a>
I wish Git would have some kind of command-server mode or libgit2 was supported with Magit to prevent needing to create new processes on Windows. Magit sometimes creates dozens of Git processes for a single operation, but because process creation is much slower on Windows than Linux, it makes Magit unusable for me on those systems. (Sadly, I don't always get a choice to just use Linux.) Simple things like magit-status take 10 seconds per refresh/stage/unstage instead of half a second elsewhere. It got to the point where using the git command line was much more bearable, but way more error-prone, and I miss Magit every time.<p><a href="https://magit.vc/manual/magit/Microsoft-Windows-Performance.html" rel="nofollow">https://magit.vc/manual/magit/Microsoft-Windows-Performance....</a><p><a href="https://github.com/magit/magit/issues/2959" rel="nofollow">https://github.com/magit/magit/issues/2959</a>
Emacs is too laggy for me as my main editor.<p>But Magit is so good that I start emacs up just to use it as my Git interface if I can't get by just with the CLI.<p>Sadly there is no Vim plugin that is competitive. There is vimagit [1], but it's not on par.<p>[1] <a href="https://github.com/jreybert/vimagit" rel="nofollow">https://github.com/jreybert/vimagit</a>
Magit is definitely one of the best addons for Emacs.<p>Nice to see Forge getting some attention. One less reason to ever leave Emacs is always welcome.
When I switched to emacs, I thought org-mode and repl integration would be the killer features. I was wrong- Magit is best emacs feature by far.<p>It’s great that parts of the magit experience have been separated into packages. Perhaps now mercurial, perforce etc can get clients similar to magit in quality.
I never fail to see so many high things about Magit and I believe they are rightly placed.<p>I am a non Emac user and wonder why no one tries to bring something similar client for non Emac population.
Magit is incredible and Emacs is my main Editor. Reading the post a couple days ago on text selection and how hard it is to get right makes me even more in awe of what a text editor does
Magit hits the sweet spot between flexible and easy that makes it an actually useful git editor integration. You still need to know git to use it, though!
Just a trivia info (I guess that's how it's called?) - especially interesting for mathematics lovers: the creator of Magit is Jonas Bernoulli, from Basel. Probably a descendant of the famous Bernoullis <a href="https://en.wikipedia.org/wiki/Bernoulli_family" rel="nofollow">https://en.wikipedia.org/wiki/Bernoulli_family</a><p>p.s. Somebody correct me if I'm wrong.
I haven't tried very hard yet, but magic has been fairly unintuitive for me. Perhaps it's just that I've been using git for so long.<p>There have been several times that I tried something with magit, and messed things up enough that I just dropped into a shell and did everything with the git command line
Tried it once. It seemed cute. That lasted precisely up to the point where I did a "git rebase -i" and landed in some crazy custom mode where I was supposed to use... I dunno, secret keybindings or something instead of just reordering the patches like I've done for years and years.<p>It went right in the trash and I haven't looked back. Do. Not. Break. Workflows. Ever. If a user knows they're supposed to open a file in a specific format in their editor, and you inject your pixie dust into the guts of their editor thinking you know better what they want to do than they do, then all you've done is <i>prove to the user that you cannot be trusted to support their work</i>.<p>Seriously: I don't use magit and don't want to learn its new tooling because I don't trust it not to break <i>itself</i>.