From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "Clément Aubert"
<aubert.clement-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Empty item introduced in list inside description for md to tex
Date: Wed, 09 Jun 2021 15:32:09 -0700 [thread overview]
Message-ID: <m2mtryvfdi.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CAPGHSeyhW5Cj4nrBdtaNgpkj_=pcEXLusFQgkz86ivEtQZBtbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Clément Aubert <aubert.clement-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> If a definition list ( https://pandoc.org/MANUAL.html#definition-lists )
> starts with a list, then an empty item seems to be inserted when converting
> to latex.
>
> Problem 1
> ~
> #. Circle the keywords
This doesn't parse as a definition list at all.
I assume you meant
Problem 1
~ #. Circle the keywords
where I do see the \item[].
The answer can be found in the source code for the LaTeX writer:
return $ text ("\\begin{enumerate}" <> inc)
$$ stylecommand
$$ resetcounter
$$ spacing
-- force list at beginning of definition to start on new line
$$ (if isFirstInDefinition then "\\item[]" else mempty)
$$ vcat items
$$ "\\end{enumerate}"
The empty \item[] was added for a reason: because without it,
the list will start on the same line as the definition, and
subsequent items won't be aligned.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m2mtryvfdi.fsf%40MacBook-Pro-2.hsd1.ca.comcast.net.
prev parent reply other threads:[~2021-06-09 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 17:00 Clément Aubert
[not found] ` <CAPGHSeyhW5Cj4nrBdtaNgpkj_=pcEXLusFQgkz86ivEtQZBtbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-09 22:32 ` John MacFarlane [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=m2mtryvfdi.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=aubert.clement-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).