From: Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: docx: verbatim blocks inside lists
Date: Fri, 31 Jul 2020 13:33:10 +0300 [thread overview]
Message-ID: <20200731133310.1641fbf33411351ea9b9a4c6@gmail.com> (raw)
In-Reply-To: <m25za423h8.fsf@johnmacfarlane.net>
John MacFarlane:
> See the manual:
> https://pandoc.org/MANUAL.html#block-content-in-list-items
>
> Now pandoc conforms to commonmark's indentation rules.
> What you need is a 4-space indent past the beginning of
> the list item content. Since your first item begins after
> a three character indent, you need 7 spaces for indented
> code.
>
> If you want to retain the 8-space indent for the code, you
> could use two spaces after the `1.`, or or you can use the
> four_space_rule extension to regain the legacy behavior.
Ah, thanks. I should not have exepected `Pandoc' would
break compatibility with the original Markdown syntax in
addition to extending it...
--
Please, do not forward replies to the list to my e-mail.
next prev parent reply other threads:[~2020-07-31 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 17:43 Anton Shepelev
[not found] ` <20200730204336.90c51e49492120edaa7f4113-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-30 19:43 ` John MacFarlane
2020-07-31 10:33 ` Anton Shepelev [this message]
[not found] ` <20200731133310.1641fbf33411351ea9b9a4c6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-31 13:54 ` Daniel Staal
2020-07-31 17:42 ` Anton Shepelev
[not found] ` <20200731204250.e744c6b967a526f35e617a1a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-07-31 19:00 ` Albert Krewinkel
2020-07-31 18:59 ` BPJ
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=20200731133310.1641fbf33411351ea9b9a4c6@gmail.com \
--to=anton.txt-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).