Johannes Sixt <> writes:

> Am 4/18/2013 19:05, schrieb Junio C Hamano:
>> Johannes Sixt <> writes:
>>> From: Johannes Sixt <>
>>> MSYS bash interprets the slash in the argument core.commentchar="/"
>>> as root directory and mangles it into a Windows style path. Use a
>>> different core.commentchar to dodge the issue.
>>> Signed-off-by: Johannes Sixt <>
>>> ...
>>> -   git -c core.commentchar="/" fmt-merge-msg --log=5 <.git/FETCH_HEAD 
>>> >actual &&
>>> +   git -c core.commentchar="x" fmt-merge-msg --log=5 <.git/FETCH_HEAD 
>>> >actual &&
>> Sigh... Again?
>> Are folks working on Msys bash aware that sometimes the users may
>> want to say key=value on their command line without the value
>> getting molested in any way and giving them some escape hatch would
>> help them?  Perhaps they have already decided that it is not
>> feasible after thinking about the issue, in which case I do not have
>> new ideas to offer.
> What is "the issue"? And in which way would an escape hatch help us here?

When the user passes key=value and value begins with a slash, value
may be a path in the filesystem very often, and adjusting it to the
local filesystem convention helps Windows users a lot.

But there are cases outside that very often when the user wants the
value passed literally.  There seems to be no way to do so.

That is the issue I was wondering. If there is a clean solution to
disable path mangling per token, we could cleanly solve it.

For example, while making sure that a value that begins with slash
in normal cases is still adjusted, i.e. mangling all of the

        xyzzy key=/a/b/c
        xyzzy key="/a/b/c"
        value=/a/b/c; xyzzy key="$value"
        value=/a/b/c; xyzzy "key=$value"

if bash could be told with a very unnatural and not so hard to type
way that the particular value is not to be mangled, e.g.

        xyzzy key="""/a/b/c"""
        value=/a/b/c; xyzzy """key=$value"""

which a normal bash would interpret as the concatenation of an empty
string inside dq, /a/b/c/ (or key=$value) inside dq, and an empty
string inside dq, which is the same as /a/b/c (or key=$value) inside
dq, it would help the less common case.  Nobody would type a string
surrounded by two empty strings to be concatenated on purpose
(i.e. very unnatural) and typing the same dq four more times than
you would normally do is not too much of a hassle (not so hard to
type).  The problematic case can then be fixed to

        git -c core.commentchar="""/""" fmt-merge-msg ...

and it will work the same way on and off Windows.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to