From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Treating changes in quoted nesting as paragraph breaks
Date: Thu, 19 Sep 2019 11:29:44 -0700 [thread overview]
Message-ID: <yh480ksgosf8br.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <93cba32f-bf2d-bec8-bb96-58be123e3a0b-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
Try with -f gfm or -f commonmark.
Pandoc requires a blank line before a block quote but these
formats don't.
Note, however, that you'll still have problems with
> > a
> b
because of laziness, this is interpreted as
blockquote (blockquote (a b)).
Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
> I often get email with nested quoting that looks like this:
>
> ```
>> This is a quoted line.
>> > This is a nested quoted line. Wrapping the first line won't
>> > touch this one.
>> And continuing with a third line.
> ```
>
> When I process such quotes with pandoc, with wrapping, it sees it
> as a single paragraph and makes a mess of it -- understandably.
>
> Would it be possible to process these a bit smarter?
>
> --
> 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/93cba32f-bf2d-bec8-bb96-58be123e3a0b%40reagle.org.
prev parent reply other threads:[~2019-09-19 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 16:49 Joseph Reagle
[not found] ` <93cba32f-bf2d-bec8-bb96-58be123e3a0b-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-09-19 18:29 ` 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=yh480ksgosf8br.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@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).