From: Junio C Hamano <gitster@pobox.com>
To: "Jean-Noël Avila" <jn.avila@free.fr>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org,
Kristoffer Haugsbakk <code@khaugsbakk.name>
Subject: Re: [PATCH v2] doc: change the markup of paragraphs following a nested list item
Date: Sun, 28 Sep 2025 08:35:01 -0700 [thread overview]
Message-ID: <xmqqo6qu7fq2.fsf@gitster.g> (raw)
In-Reply-To: <20250927195032.37223-1-jn.avila@free.fr> ("Jean-Noël Avila"'s message of "Sat, 27 Sep 2025 21:39:45 +0200")
Jean-Noël Avila <jn.avila@free.fr> writes:
> Asciidoctor and asciidoc.py have different behaviors when a paragraph
> follows a nested list item. Asciidoctor has a bug[1] that makes it keep a
> plus sign (+) used to attached paragraphs at the beginning of the paragraph.
>
> This commit uses workarounds to avoid this problem by using second level
> definition lists and open blocks.
>
> [1]:https://github.com/asciidoctor/asciidoctor/issues/4704
>
> Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
> ---
>
> Sorry for the straight/stray confusion. It is saner to remove it.
>
> The first occurrence of the described issue is a few lines below where you
> looked at:
>
> https://git.github.io/htmldocs/git-config.html#:~:text=+%20For%20historical
>
> also see the second one:
>
> https://git.github.io/htmldocs/git-log.html#:~:text=%2B%20%25(decorate
>
> And big thank you to peff for teaching doc-diff.
Thanks!
next prev parent reply other threads:[~2025-09-28 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 18:34 doc: config/extensions.adoc: line continuation syntax error Kristoffer Haugsbakk
2025-09-23 21:08 ` Jean-Noël AVILA
2025-09-24 0:54 ` Jeff King
2025-09-26 19:40 ` [PATCH] doc: change the markup of paragraphs following a nested list item Jean-Noël Avila
2025-09-26 20:54 ` Junio C Hamano
2025-09-27 19:39 ` [PATCH v2] " Jean-Noël Avila
2025-09-28 15:35 ` Junio C Hamano [this message]
2025-10-03 3:11 ` Jeff King
2025-10-03 3:41 ` Jeff King
2025-10-03 16:29 ` Junio C Hamano
2025-10-04 17:31 ` Jean-Noël AVILA
2025-10-10 16:11 ` Junio C Hamano
2025-10-10 22:23 ` Jeff King
2025-10-13 15:17 ` Junio C Hamano
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=xmqqo6qu7fq2.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=peff@peff.net \
/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).