Thank you PJ... yes you are exactly correct. I'm not clear, though,
why the mvim default in this scenario is to open in background.

On Mar 22, 11:01 am, PJ Weisberg <> wrote:
> On Wednesday, March 21, 2012, Les Nightingill <>
> wrote:> Solved! (not entirely sure why, though!). Posting the solution here 
> for
> future Googlers.
> > The solution is on StackOverflow
> > The solution is this configuration:
> > git config --global core.editor "mvim -f"
> In general, any editor that opens itself *in the background* is not going
> to work.  When the editor hands control back to Git, Git thinks it's
> because you're done editing.  Any other command-line tool that uses $EDITOR
> will have the same issue.
> I'll bet you saw a blank file because Git deleted the file (which it
> thought you were done with) before mvim got around to opening it.
> --
> -PJ
> Gehm's Corollary to Clark's Law: Any technology distinguishable from
> magic is insufficiently advanced.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to