From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Matt Kraai <kraai@ftbfs.org>,
git@vger.kernel.org, Philip Oakley <philipoakley@iee.org>,
Matthew Kraai <matt.kraai@abbott.com>
Subject: Re: [PATCH] Documentation: remove unnecessary backslashes
Date: Wed, 20 Jan 2016 15:34:30 -0500 [thread overview]
Message-ID: <20160120203430.GB6092@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqmvs05722.fsf@gitster.mtv.corp.google.com>
On Wed, Jan 20, 2016 at 12:28:53PM -0800, Junio C Hamano wrote:
> >> -'<refname>@\{<date>\}', e.g. 'master@\{yesterday\}', 'HEAD@\{5 minutes ago\}'::
> >> +'<refname>@{<date>}', e.g. 'master@\{yesterday\}', 'HEAD@{5 minutes ago}'::
> >
> > I see you didn't tweak the middle one here, because it _does_ look like
> > an attribute. Does asciidoctor actually remove the backslashes there?
>
> A more important question is if it works without the backslashes.
> If not-too-stale versions of asciidoc everybody uses these days are
> all OK without braces quoted with backslashes, and if the same holds
> true for asciidoctor, then we would want consistency here.
The answer to that is implied in the original commit message; no, it
does not work, because it is syntactically an asciidoc attribute.
> On the other hand, if this line must be spelled like the above to
> please asciidoctor, i.e. the first and the last must not have
> backslashes and the second must have backslashes, I'd have to say
> we have a bigger problem. Perhaps asciidoctor needs to be fixed
> until normal people like we can rely on it.
Yeah, that is the "insane" part I mentioned. It _does_ make sense
syntactically ("-1" cannot possibly be an attribute name, so it does not
parse as one), but I do not like the degree to which writers must know
all of the arcane syntax rules (and cannot rely on something simple like
"{ is special, so I must escape it, and over-escaping is not a
problem").
-Peff
next prev parent reply other threads:[~2016-01-20 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 17:21 [PATCH] Documentation: remove unnecessary backslashes Matt Kraai
2016-01-20 18:24 ` Jeff King
2016-01-20 20:28 ` Junio C Hamano
2016-01-20 20:34 ` Jeff King [this message]
2016-01-22 2:46 ` brian m. carlson
2016-01-20 21:35 ` Matt Kraai
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=20160120203430.GB6092@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kraai@ftbfs.org \
--cc=matt.kraai@abbott.com \
--cc=philipoakley@iee.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).