All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: Tait <git.git@t41t.com>
Cc: git@vger.kernel.org
Subject: Re: using gvim as editor on Windows
Date: Tue, 9 Mar 2010 00:32:09 +0100	[thread overview]
Message-ID: <201003090032.10037.markus.heidelberg@web.de> (raw)
In-Reply-To: <20100308185439.GO2480@ece.pdx.edu>

Tait, 2010-03-08 19:54:
> > > 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

  reply	other threads:[~2010-03-09 12:22 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
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 [this message]
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=201003090032.10037.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.