magit

Meta-answer: type 'b' in the magit status buffer and take a look at the help.

If you're an emacs and git user but don't use magit, it's a big, big waste of the powers of emacs.

In fact magit could probably do some of this with a hook on reordering commits which would not require more git metadata.

Very very minor nitpick, magit-status theme (gray, brown, black) is not very welcoming.

Besides Emacs itself, Magit is the greatest tool in my arsenal for making clean patches and making me a more productive programmer in general.

This is because my fingers still want to exercise the magit 1.

Sure I could use another GUI, but magit is very easy when I'm already in emacs.

Using emacs + magit I can rebase and look at per commit files whilst having a buffer open to re-order commits.

I use magit at work and we have to all use the same git version.

So that one part is not a selling point for magit.

I appreciate how Magit isn't something that takes away from the git experience by holding your hands like a GUI might.

Even if you don't use Emacs, I believe you _have_ to try magit.

For me the command "M-x magit-version" is not defined until after I run "M-x magit-status".

But (emacs 24.5.1 OSX) when I type "M-x package-install" it claims magit [No Match] I use emacs- but I don't tend to customize it much.

(defvar packages '(pkg1 pkg2 magit)) (require 'package) (add-to-list 'package-archives '("melpa".

Magit is just an efficient interface that in the end is just like using standard git in the command line.

With Magit, at least in my experience, you are more inclined to write better commits.

Magit pushed my change directly to refs/heads instead of refs/for, completely bypassing gerrit code review.