From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Milan Bracke
<milan.bracke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Proposed new list type
Date: Tue, 25 May 2021 09:49:53 -0700 [thread overview]
Message-ID: <m2czte21xq.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <11e20690-21cc-4287-81b0-e5f3e191cf1bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
> with a third solution. The main drawback was that these lists without
> markers
> are often used to add paragraphs in a list item without visually adding a
> new
> list element or ending the list. By using paragraphs, we would visually end
> the
> list. My solution to this is to add the list items without markers as
> paragraphs to the last item of the list immediately before if there is one.
I don't really like this, because it modifies the structure, and
pandoc is about preserving structure. Conceptually, these items
aren't children of the last list item with a marker, even they
render similarly. Besides, what if the entire list consists
of these unmarked items, and there isn't a marked item to put
them under?
next prev parent reply other threads:[~2021-05-25 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 14:29 Milan Bracke
[not found] ` <4e936aa2-41d6-4d68-ba5a-bea916754922n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-04 17:39 ` John MacFarlane
[not found] ` <m2mtta1jr7.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-11 14:04 ` Milan Bracke
[not found] ` <11e20690-21cc-4287-81b0-e5f3e191cf1bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-25 13:20 ` Milan Bracke
2021-05-25 16:49 ` John MacFarlane [this message]
[not found] ` <m2czte21xq.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-26 8:40 ` Milan Bracke
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=m2czte21xq.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=milan.bracke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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).