From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Is there an official syntax for specifying markdown extensions in a YAML block?
Date: Sun, 13 Sep 2015 21:11:35 -0700 [thread overview]
Message-ID: <20150914041135.GA35733@MacBook-Air.local> (raw)
In-Reply-To: <ef28e782-4328-4018-aec8-c6fc2719fb19-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
No, YAML blocks only affect metadata. They don't affect
the input format, which currently must be specified on the
command line.
+++ Brian Danielak [Sep 13 15 15:25 ]:
> I asked this question on
> StackOverflow: http://stackoverflow.com/questions/32492145/how-can-i-sp
> ecify-pandocs-markdown-extensions-using-a-yaml-block
> [1]Someone answered with a way to specify those options using RMarkdown
> it: http://rmarkdown.rstudio.com/pdf_document_format.html#markdown-exte
> nsions
> But, I couldn't find that particular technique documented anywhere on
> the current [2]Pandoc User's Guide, so:
> 1. Is the above solution an officially-supported way to specify
> markdown extensions in a YAML block?
> 2. If so, why did I have such a hard time finding it in the Pandoc
> User's Guide? Did I miss it?
> 3. If it's not currently in the Pandoc User's guide, should it be? (My
> opinion is yes, but I don't know that I'm representative of a
> common use case.)
> 4. If this mechanism should be documented in the Pandoc User's Guide,
> is there a way I can help?
>
> - B
>
> --
> 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 [3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [4]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [5]https://groups.google.com/d/msgid/pandoc-discuss/ef28e782-4328-4018-
> aec8-c6fc2719fb19%40googlegroups.com.
> For more options, visit [6]https://groups.google.com/d/optout.
>
>References
>
> 1. http://stackoverflow.com/a/32492257/180626
> 2. http://pandoc.org/README.html
> 3. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 4. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 5. https://groups.google.com/d/msgid/pandoc-discuss/ef28e782-4328-4018-aec8-c6fc2719fb19-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 6. https://groups.google.com/d/optout
prev parent reply other threads:[~2015-09-14 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 22:25 Brian Danielak
[not found] ` <ef28e782-4328-4018-aec8-c6fc2719fb19-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-09-13 23:08 ` Ivan Lazar Miljenovic
2015-09-14 4:11 ` 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=20150914041135.GA35733@MacBook-Air.local \
--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).