From: Jacob Helwig <jacob.helwig@gmail.com>
To: Tait <git.git@t41t.com>
Cc: git@vger.kernel.org
Subject: Re: using gvim as editor on Windows
Date: Fri, 5 Mar 2010 23:22:34 -0800 [thread overview]
Message-ID: <8c9a061003052322v446acddbm5792038af450d0b9@mail.gmail.com> (raw)
In-Reply-To: <20100306070628.GM2480@ece.pdx.edu>
On Fri, Mar 5, 2010 at 23:06, Tait <git.git@t41t.com> wrote:
>
> I'd prefer to use gvim as an editor on Windows XP instead of vim. (I also
> prefer it as a difftool, but that's a separate issue.) Gvim releases
> the terminal when it launches, which git doesn't like too much. So I
> create gvimf.cmd in my path and use it for core.editor. Gvimf.cmd is
> quite simple; it calls:
> start "dummy" /b /wait "C:\Program Files\Vim\vim72\gvim.exe" %*
>
> In .gitconfig:
> [core]
> editor = gvimf.cmd
>
> This works well enough for git commit. However, git rebase -i is not
> happy. It errors:
> C:\path to\repo> git rebase -i HEAD~10
> The system cannot find the file dummy.
> Could not execute editor
>
> Okay, I can fix that. I change core.editor to "cmd \\/c gvimf.cmd". (This
> is the same pattern I use for gvim as a difftool.) Now my .gitconfig has:
> [core]
> editor = cmd \\\\/c gvimf.cmd
>
> Git rebase is happy, but git commit is not. It errors:
> C:\path to\repo> git commit
> 'OMMIT_EDITMSG' is not recognized as an internal or external command,
> operable program or batch file.
> error: There was a problem with the editor 'cmd \\/c gvimf.cmd'.
> Please supply the message using either -m or -F option.
>
> In the selfish hope to avoid work, has anyone else already encountered
> and solved how to use gvim as an editor?
>
> Tait
>
Use the -f (stay in the foreground) flag. I haven't tried this in
Windows, but that's how I've used it in Linux.
[core]
editor = gvim -f
next prev parent reply other threads:[~2010-03-06 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 7:06 using gvim as editor on Windows Tait
2010-03-06 7:22 ` Jacob Helwig [this message]
2010-03-06 7:37 ` Tait
2010-03-06 12:17 ` Markus Heidelberg
2010-03-08 18:54 ` Tait
2010-03-08 23:32 ` Markus Heidelberg
2010-03-09 2:45 ` Tait
2010-03-09 20:07 ` Junio C Hamano
2010-03-11 9:04 ` Tait
2010-03-11 9:36 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c9a061003052322v446acddbm5792038af450d0b9@mail.gmail.com \
--to=jacob.helwig@gmail.com \
--cc=git.git@t41t.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).