git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation: remove unnecessary backslashes

From
MKMatt Kraai <kraai@ftbfs.org>
Date
Jan 20, 2016, 21:35 UTC
Message-ID
<20160120213512.GA10192@ftbfs.org>
In-Reply-To
<20160120182421.GA27562@sigill.intra.peff.net>
Hi,
On Wed, Jan 20, 2016 at 01:24:21PM -0500, Jeff King wrote:
Show 6 quoted lines
> 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.

Show 7 quoted lines
> > -'<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/
Previous: brian m. carlson
Message 6 of 6 in “Documentation: remove unnecessary backslashes”
  1. Documentation: remove unnecessary backslashesMatt Kraai, Jan 20, 2016
  2. Jeff KingJan 20, 2016
  3. Junio C HamanoJan 20, 2016
  4. Jeff KingJan 20, 2016
  5. brian m. carlsonJan 22, 2016
  6. Matt KraaiJan 20, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.