> > On Windows, gvim -f is basically a shortcut for the start invocation I > > pasted above. > > Not necessarily. You can avoid using the .bat wrappers from C:\Windows, > which cause the problem, but use gvim.exe directly by setting your PATH > appropriately. It will also work for git-difftool. I was hoping for a little more life in this thread. Does calling the .exe directly work for you? If I call gvim.exe directly (with or without -f -- it doesn't matter), it opens a new file called $@. After quitting, the commit is aborted for lack of a commit message. I can do an ugly work-around by making core.editor "gvim.exe -f $@" but then gvim opens two buffers, one for the commit message and another for the literal $@. With rebase -i, calling the executable directly (with or without -f) works to open the commit list. Rebase -i with $@ in the setting fails. It appears the filename is not quoted correctly and vim is opening multiple buffers with various components of the path name as filenames. The problem seems to be unique to me, so I'll find some time to look at what rebase and/or commit are doing wrong. Tait -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html