public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Ken Cunningham <kencpcunningham-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Is there a way to enforce lazy block quotation syntax in Markdown output?
Date: Mon, 17 Jan 2022 22:27:50 -0800 (PST)	[thread overview]
Message-ID: <1d63989b-0e60-4741-bcfb-86a2a8e09a5an@googlegroups.com> (raw)
In-Reply-To: <6051f734ea2348a398b41f582ee0c693-NSENcxR/0n0@public.gmane.org>


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

It is indeed; thank you!

On Tuesday, January 18, 2022 at 5:25:01 PM UTC+11 denis...-NSENcxR/0n0@public.gmane.org wrote:

> You can specify line wrapping with the --wrap option. Maybe --wrap=none is 
> what you want?
>
>  
>
> Denis
>
>  
>
> *Von:* pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> *Im 
> Auftrag von *Ken Cunningham
> *Gesendet:* Dienstag, 18. Januar 2022 07:21
> *An:* pandoc-discuss <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
> *Betreff:* Is there a way to enforce lazy block quotation syntax in 
> Markdown output?
>
>  
>
> I'm converting from Markdown to Markdown in order to expand citations, as 
> described here:
>
> https://groups.google.com/g/pandoc-discuss/c/HM0y16gENfc
>
>  
>
> My input files use the 'lazy' block quotation syntax (a `>` preceding each 
> block and blank line); the output is line-wrapped, with a `>` on each line. 
> Is there a way to suppress this behaviour?
>
>  
>
> To put my question more generally, is it possible to use Pandoc to expand 
> citations only?
>
>  
>
> Thanks for the indispensable software.
>
> -- 
> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/74661bf8-fa80-4359-b43b-ffc43d75a1a9n%40googlegroups.com 
> <https://groups.google.com/d/msgid/pandoc-discuss/74661bf8-fa80-4359-b43b-ffc43d75a1a9n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/1d63989b-0e60-4741-bcfb-86a2a8e09a5an%40googlegroups.com.

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

      parent reply	other threads:[~2022-01-18  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHYDDOCzxW97zu8/0e9VnRfbTkZBKxoTusQ>
2022-01-18  6:20 ` Ken Cunningham
     [not found]   ` <74661bf8-fa80-4359-b43b-ffc43d75a1a9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-18  6:24     ` AW: " denis.maier-NSENcxR/0n0
     [not found]       ` <6051f734ea2348a398b41f582ee0c693-NSENcxR/0n0@public.gmane.org>
2022-01-18  6:27         ` Ken Cunningham [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=1d63989b-0e60-4741-bcfb-86a2a8e09a5an@googlegroups.com \
    --to=kencpcunningham-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).