From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Zeng.Shixin@gmail.com, theevancarroll@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH] launch_editor(): allow spaces in the filename
Date: Mon, 10 Mar 2008 14:48:36 -0700 [thread overview]
Message-ID: <7vabl6i72j.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vejaii7c5.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 10 Mar 2008 14:42:50 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> ...
>> This fixes
>>
>> git config core.editor "c:/Program Files/What/Ever.exe"
>>
>
> Having sent a few messages about shell quoting, it makes me wonder if this
> was done very deliberately in the first place, so that you can do things
> like:
>
> git config core.editor "emacs -nw"
>
> Blame followed by list archive hunting around that timeperiod would tell.
I'll let others look for the bug report and user request from the list
archive, but the pertinent commit is 5e2de4f9 (Fix $EDITOR regression
introduced by rewrite in C.):
When git-tag and git-commit launches the editor, they used to
honor EDITOR="editor -options args..." but recent rewrite in C
insisted on $EDITOR to be the path to the editor executable.
This restores the older behaviour.
In other words, your example is a user error and your patch is a
regression.
I guess the right way to do that would be:
git config core.editor '"c:/Program Files/What/Ever.exe"'
but I do not do windows, so this is obviously untested.
next prev parent reply other threads:[~2008-03-10 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 20:42 [PATCH] launch_editor(): allow spaces in the filename Johannes Schindelin
2008-03-10 21:32 ` Johannes Sixt
2008-03-10 21:37 ` Junio C Hamano
2008-03-10 21:46 ` Johannes Sixt
2008-03-10 22:18 ` Johannes Schindelin
2008-03-10 21:33 ` Junio C Hamano
2008-03-10 21:42 ` Junio C Hamano
2008-03-10 21:48 ` Junio C Hamano [this message]
2008-03-10 22:24 ` Johannes Schindelin
2008-03-11 0:15 ` Junio C Hamano
2008-03-11 9:56 ` Johannes Schindelin
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=7vabl6i72j.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Zeng.Shixin@gmail.com \
--cc=git@vger.kernel.org \
--cc=theevancarroll@gmail.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 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.