From: Tait <git.git@t41t.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: using gvim as editor on Windows
Date: Thu, 11 Mar 2010 01:04:24 -0800 [thread overview]
Message-ID: <20100311090424.GV2480@ece.pdx.edu> (raw)
In-Reply-To: <7vzl2hw972.fsf@alter.siamese.dyndns.org>
> This says "if 'editor' is not exactly the string ':'", ...
Oh right; I ... yeah, something. (I've got no excuse for mis-thinking
that one.)
> If you end up with a file whose name literally is '$@', that probably
> means your "sh" did not expand it correctly.
It does expand the $@ when I add it explicitly to core.editor though. Maybe
it's the ""s. I'll have to figure out how to compile git for Windows
to try a patch.
Oddly enough, if I remove the : from the file path, it does work as
expected. Adding the : back introduces the faulty behavior described
earlier.
Tait
next prev parent reply other threads:[~2010-03-11 9:05 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
2010-03-09 2:45 ` Tait
2010-03-09 20:07 ` Junio C Hamano
2010-03-11 9:04 ` Tait [this message]
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=20100311090424.GV2480@ece.pdx.edu \
--to=git.git@t41t.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).