Dear vim-ers, yes I know my git.vim ftplugin was kind of a dirty hack, and that it didn't worked that well.

Since a few days, git.git next branch shows relative paths in git-status(1) and that was the last hit to my already not that stable hack. So I raised the question on the git mailing list on how to do that plug-in properly, and it happens there is a perfect solution, that was here from day 1…

So here is a new release of the plugin that uses the special index^[1] git-commit(1) builds for the occasion, hence can use git-diff(1) directly instead of parsing clumsily the commit buffer.

Direct benefits:

• it does renaming detection well;
• it works correctly when you are --amend'ing or committing something that was pushed to the index, and that the corresponding files have non staged local changes;
• it's damn fast (even when you commit more than 10 files);
• you can even hide whitespaces changes, just add let git_diff_opts = "-C -C -w -b" in your .vimrc and you're done !

Here is what happens when a (mad)tty meets a (mad)mutt

Okay, for real it has zillions of usability issues right now:

• you shouldn't resize the mutt without leaving your $EDITOR first ;
• you cannot interact with the rest of mutt either ;
• …

But all those things needs a proper event loop (and anyone that ever looked at the mutt code knows that well…).

and yes it works for emacs too