Re: [Question] Complex textconv text
- Date: Fri, 14 Dec 2018 05:04:57 -0500
- From: Jeff King <peff@xxxxxxxx>
- Subject: Re: [Question] Complex textconv text
On Fri, Dec 14, 2018 at 12:12:01PM +0900, Junio C Hamano wrote:
> > I have a strange situation and need help with resolving funky characters in
> > .git/config. My situation is this:
> > [diff "*.dat"]
> > textconv = enscribe-conv
> > --format=-a1\(A=-a1,-a16,-a32\|P=-a1,-a32,-a16\|=-a1,-d,a14\),-a224
> > Basically this is a formatter for diff so that I can show structured binary
> > data. The unquoted syntax of the format string is:
> > --format=-a1(A=-a1,-a16,-a32|P=-a1,-a32,-a16|=-a1,-d,a14),-a224
> > Content is not really important. The issue is that git is reporting fatal:
> > bad config line 2 in file .git/config when I escape the (, ), and |
> > characters.
> That failure is understandable, as
> The following escape sequences (beside `\"` and `\\`) are recognized:
> `\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB)
> and `\b` for backspace (BS). Other char escape sequences (including octal
> escape sequences) are invalid.
> is what Documentation/config.txt says. \(, \) and \| is not a way
> to escape these letters from the .git/config parser (they do not
> need to be escaped from .git/config parser)..
Yes. It's a little unfriendly that we don't pass them through, since
that would do what Randall wants here. But doing so would be unfriendly
to somebody who _did_ want to quote them, and is confused why there are
passed through literally.
At any rate, the "right" way here is to quote the backslashes that are
meant to be passed through to the shell, like:
textconv = foo \\(X\\|\\)
Note that if you write the config using git-config, that's what it
$ git config -f file foo.bar '\(X\|Y\)'
$ cat file
bar = \\(X\\|Y\\)
I agree that your double-quote suggestion is more readable (or as
Randall eventually figured out, hiding it all in a real script ;) ).