Re: [PATCH v2 1/2] Documentation: Improve description for core.quotePath
- From
Jakub Narębski <jnareb@gmail.com>
- Date
- Feb 24, 2017, 21:43 UTC
- Message-ID
- <f6845604-005d-06bb-e5e6-61f683cdbaf8@gmail.com>
- In-Reply-To
- <1487968676-6126-2-git-send-email-asheiduk@gmail.com>
W dniu 24.02.2017 o 21:37, Andreas Heiduk pisze:
> Signed-off-by: Andreas Heiduk <asheiduk@gmail.com>
Thanks. This is good work.
Show 23 quoted lines
> --- > Documentation/config.txt | 24 ++++++++++++++---------- > 1 file changed, 14 insertions(+), 10 deletions(-) > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index 1fee83c..fa06c2a 100644 > --- a/Documentation/config.txt > +++ b/Documentation/config.txt > @@ -347,16 +347,20 @@ core.checkStat:: > all fields, including the sub-second part of mtime and ctime. > > core.quotePath:: > - The commands that output paths (e.g. 'ls-files', > - 'diff'), when not given the `-z` option, will quote > - "unusual" characters in the pathname by enclosing the > - pathname in a double-quote pair and with backslashes the > - same way strings in C source code are quoted. If this > - variable is set to false, the bytes higher than 0x80 are > - not quoted but output as verbatim. Note that double > - quote, backslash and control characters are always > - quoted without `-z` regardless of the setting of this > - variable. > +
This empty line should not be here, I think.
Show 6 quoted lines
> + Commands that output paths (e.g. 'ls-files', 'diff'), will > + quote "unusual" characters in the pathname by enclosing the > + pathname in double-quotes and escaping those characters with > + backslashes in the same way C escapes control characters (e.g. > + `\t` for TAB, `\n` for LF, `\\` for backslash) or bytes with > + values larger than 0x80 (e.g. octal `\302\265` for "micro" in
I wonder if we can put UTF-8 in AsciiDoc, that is write "μ" instead of spelling it "micro" (or: Greek letter "mu").
Or "µ" / "µ", though I wonder how well it is supported in manpage, info and PDF outputs...
Show 11 quoted lines
> + UTF-8). If this variable is set to false, bytes higher than > + 0x80 are not considered "unusual" any more. Double-quotes, > + backslash and control characters are always escaped regardless > + of the setting of this variable. A simple space character is > + not considered "unusual". Many commands can output pathnames > + completely verbatim using the `-z` option. The default value > + is true. > > core.eol:: > Sets the line ending type to use in the working directory for >