Re: using gvim as editor on Windows

From: Markus Heidelberg <markus.heidelberg@web.de>
Date: Mar 8, 2010, 23:32 UTC
Message-ID: <201003090032.10037.markus.heidelberg@web.de>
In-Reply-To: <20100308185439.GO2480@ece.pdx.edu>

Tait, 2010-03-08 19:54:

Show 8 quoted lines

> > > 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.

First of all: do you have the problems in cmd.exe or Git Bash or both?

> 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
> $@.

I don't know where the $@ should come from. You apparently don't invoke gvim.exe directly. git-commit is a C program, not a shell script, there should come no $@ from this side. What does invoking gvim.exe on the command line without the use of git do?

I have: core.editor=gvim -f C:\Programme\Vim\vim72 in PATH (both before or after C:\WINDOWS works here) Works with cmd.exe and Git Bash.

> 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.

I guess neither rebase nor commit are wrong in this case.

Markus