From: Matt Kraai <kraai@ftbfs.org>
To: Jeff King <peff@peff.net>
Cc: 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 13:35:12 -0800 [thread overview]
Message-ID: <20160120213512.GA10192@ftbfs.org> (raw)
In-Reply-To: <20160120182421.GA27562@sigill.intra.peff.net>
Hi,
On Wed, Jan 20, 2016 at 01:24:21PM -0500, Jeff King wrote:
> On Wed, Jan 20, 2016 at 09:21:37AM -0800, Matt Kraai 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?
Yes, asciidoctor appears to remove the backslashes in some cases but
not others. I removed the backslashes from the source if it did not
remove them. I verified that the asciidoc output isn't affected.
> > -'<refname>@\{<n>\}', e.g. 'master@\{1\}'::
> > +'<refname>@{<n>}', e.g. 'master@\{1\}'::
>
> Ditto here for "1". IMHO asciidoctor's behavior is somewhat crazy, as it
> means you have to know arcane quoting rules to get correct output (you
> cannot just err on the side of quoting). But it's probably still worth
> working around.
I couldn't find any documentation of asciidoctor's behavior. I didn't
try figuring the behavior out from asciidoctor's source code.
--
Matt https://ftbfs.org/~kraai/
prev parent reply other threads:[~2016-01-20 21:35 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
2016-01-22 2:46 ` brian m. carlson
2016-01-20 21:35 ` Matt Kraai [this message]
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=20160120213512.GA10192@ftbfs.org \
--to=kraai@ftbfs.org \
--cc=git@vger.kernel.org \
--cc=matt.kraai@abbott.com \
--cc=peff@peff.net \
--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 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.