From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Stupid quoting...
Date: Wed, 20 Jun 2007 10:40:26 +0200 [thread overview]
Message-ID: <f5ap5r$sj7$2@sea.gmane.org> (raw)
In-Reply-To: 86y7ifoykt.fsf@lola.quinscape.zz
David Kastrup wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>>
>>>> I don't see our discourse leading anywhere: the points have been made.
>>>
>>> I would really, really, really like to see a solution. Alas, I
>>> cannot think of one, other than _forcing_ the developers to use
>>> ASCII-only filenames.
>>> Note that there is no convention yet in Git to state which encoding
>>> your filenames are supposed to use. And in fact, we already had a
>>> fine example in git.git why this is particularly difficult. MacOSX
>>> is too clever to be true, in that it gladly takes filenames in one
>>> encoding, but reads those filenames out in _another_
>>> encoding. Thus, a "git add <filename>" can well end up in
>>> git-status saying that a file was deleted, and another file
>>> (actually the same, but in a different encoding) is untracked.
>>
>> Having said that, the absolute minimum that needs to be quoted are
>> double-quote (because it is used by quoting as agreed with GNU
>> diff/patch maintainer), backslash (used to introduce C-like
>> quoting),
>> newline and horizontal tab (makes "patch" confused, as it would make
>> it ambiguous where the pathname ends), so I am not opposed to a
>> patch that introduces a new mode, probably on by default _unless_ we
>> are generating --format=email, that does not quote high byte values.
>
> I think it would be ok to quote non-graphic characters with octal
> escape sequences. On ASCII-based systems, those are the characters
> 0x00 to 0x1f. They don't have a visual representation of their own,
> anyway. _IF_ they appear in filenames, it is certainly a case
> involved with excessive cleverness and/or garbage. I'd leave the rest
> alone.
By the way, ls(1) has its --quoting-style=WORD option, why shouldn't
git-diff and friends (including git-format-patch) have the same? And we
could change the default later on...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-06-20 8:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 11:30 Stupid quoting David Kastrup
2007-06-13 12:06 ` Alex Riesen
2007-06-13 12:21 ` Johannes Schindelin
[not found] ` <86ejkgvxmb.fsf@lola.quinscape.zz>
2007-06-14 0:51 ` Johannes Schindelin
2007-06-14 6:12 ` David Kastrup
2007-06-14 7:06 ` Alex Riesen
[not found] ` <86hcpb6lr6.fsf@lola.quinscape.zz>
2007-06-14 8:51 ` Alex Riesen
2007-06-14 1:06 ` Steven Grimm
2007-06-14 1:12 ` Johannes Schindelin
2007-06-14 1:19 ` Steven Grimm
2007-06-14 1:34 ` Johannes Schindelin
2007-06-14 8:49 ` Junio C Hamano
2007-06-16 21:03 ` Jakub Narebski
2007-06-18 8:00 ` David Kastrup
2007-06-18 16:19 ` Jeff King
2007-06-19 1:00 ` Johannes Schindelin
2007-06-19 7:44 ` David Kastrup
2007-06-19 9:50 ` Johannes Schindelin
2007-06-19 20:53 ` Olivier Galibert
[not found] ` <86645kutow.fsf@lola.quinscape.zz>
2007-06-20 2:19 ` Johannes Schindelin
2007-06-20 6:19 ` Junio C Hamano
2007-06-20 7:49 ` David Kastrup
2007-06-20 8:40 ` Jakub Narebski [this message]
2007-06-20 8:59 ` David Kastrup
2007-06-24 6:50 ` Jan Hudec
2007-06-24 11:14 ` Robin Rosenberg
2007-06-24 11:47 ` Junio C Hamano
2007-06-24 11:58 ` David Kastrup
2007-06-24 12:19 ` Junio C Hamano
2007-06-24 12:41 ` Jeff King
2007-06-24 16:25 ` Jan Hudec
2007-06-24 19:39 ` Robin Rosenberg
2007-06-24 19:47 ` David Kastrup
2007-06-24 20:17 ` Robin Rosenberg
2007-06-24 20:25 ` David Kastrup
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='f5ap5r$sj7$2@sea.gmane.org' \
--to=jnareb@gmail.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.