From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Disabling blank_before_blockquote still requires blank lines
Date: Wed, 4 Oct 2017 10:23:05 -0700 [thread overview]
Message-ID: <20171004172305.GD20306@protagoras> (raw)
In-Reply-To: <841af626-55cb-4baf-a65a-af600387a914-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
That's because of "laziness." Markdown allows you to lazily
omit `>` markers after the first line of a paragraph.
So,
>> quote
quote
is a block quote with "quote quote", and so is
>> quote
> quote
+++ Francisco Lopes [Oct 03 17 22:47 ]:
> Hi, with command line "pandoc -f markdown-blank_before_blockquote"
> for this content:
> ## Quotes
> > quoted
> >> quoted
> >> more quotes
> > text
> > content
> I get an HTML that's like:
> Quotes
> quoted
> quoted more quotes text content
> As you can see, the second level blockquote gets glued with the single
> level one in the end,
> the fix I know for this is to insert a blank line:
> ## Quotes
> > quoted
> >> quoted
> >> more quotes
> >
> > text
> > content
> then I get:
> Quotes
> quoted
> quoted more quotes
> text content
> Notice that I'm using "-blank_before_blockquote" with hopes to not have
> to insert this additional
> blank lines, but it's just working from lower level quotation to inner,
> not back. Is there an option?
> If not, would it be OK to support this?
> Regards
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/841af626-55cb-4baf-
> a65a-af600387a914%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/841af626-55cb-4baf-a65a-af600387a914-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-10-04 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 5:47 Francisco Lopes
[not found] ` <841af626-55cb-4baf-a65a-af600387a914-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-04 5:50 ` Francisco Lopes
2017-10-04 17:23 ` John MACFARLANE [this message]
2017-10-04 17:56 ` Francisco Lopes
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=20171004172305.GD20306@protagoras \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).