public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Francisco Lopes <francisco.mailing.lists-iwoE/Jjr5LLQT0dZR+AlfA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Disabling blank_before_blockquote still requires blank lines
Date: Wed, 4 Oct 2017 10:56:20 -0700 (PDT)	[thread overview]
Message-ID: <26106523-6bd5-4e7b-bc20-6ab4cc6b8c70@googlegroups.com> (raw)
In-Reply-To: <20171004172305.GD20306@protagoras>


[-- Attachment #1.1: Type: text/plain, Size: 2297 bytes --]

Hi John,

Thanks for recalling me this, now I realize why but.... I really don't wish 
this behavior :( Personally I rarely use
lazyness, even outside of this context I'm actually dealing with, which is 
block quotes for email. So, if there's no
way to disable lazyness at the moment, is it a worth request to have such a 
option?

Regards

Em quarta-feira, 4 de outubro de 2017 14:23:05 UTC-3, John MacFarlane 
escreveu:
>
> 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 pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/26106523-6bd5-4e7b-bc20-6ab4cc6b8c70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 431661 bytes --]

      reply	other threads:[~2017-10-04 17:56 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
2017-10-04 17:56     ` Francisco Lopes [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=26106523-6bd5-4e7b-bc20-6ab4cc6b8c70@googlegroups.com \
    --to=francisco.mailing.lists-iwoe/jjr5llqt0dzr+alfa@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).