Re: [PATCH v2 3/3] doc: git-config: escape erroneous highlight markup

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 11, 2026, 17:33 UTC
Message-ID: <xmqqjys5nfsc.fsf@gitster.g>
In-Reply-To: <20260611083139.GA2237523@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 8 quoted lines

> Using backticks does work, though it always opens a typographical
> question. When reading the source, you see `#`, so you get a punctuation
> delimiter but no typographical one. In the rendered output, you'll see
> it in a typewriter font (assuming we fix the config issue), but we'd
> lose the visible punctuation. I could live with that.
> ...
> you might hope by asciidoc. Doing `" # "` does work, and is probably OK
> enough here.

Yucky, yucky, asciidoc. I think these literal notation `#` would be a good way forward, given the constraints.

Thanks.

$ 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.