From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Use of YAML metadata block
Date: Sat, 9 Apr 2016 10:18:19 -0700 [thread overview]
Message-ID: <20160409171819.GA64852@MacBook-Air-2.local> (raw)
In-Reply-To: <57090C95.6050607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
+++ R (Chandra) Chandrasekhar [Apr 09 16 19:37 ]:
>I am a little unsure of the boundaries of what a YAML metadata block
>can contain in order for it to be correctly interpreted as a command
>line option.
>
>While there is a certain allure to having all compile-time options
>sitting in a metadata block in the document itself to make it
>self-contained, Pandoc's versatility in format support makes this
>difficult to achieve.
>
>My understanding is that key-value options to --variable and
>--metadata can be included in a YAML metadata block, but not standard
>command line options like --bibliography or --filter or
>--highlight-style (with title, author, date being exceptions.)
>
>Is this correct?
Yes, but with one qualification: some command-line options,
like `--bibliography`, do nothing but set a metadata value.
So that's a case where you can put it in your YAML metadata.
The section of the User's Guide/man page/README entitled
Variables is the best place to look for what can
be set in YAML metadata.
prev parent reply other threads:[~2016-04-09 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 14:07 R (Chandra) Chandrasekhar
[not found] ` <57090C95.6050607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-09 17:18 ` 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=20160409171819.GA64852@MacBook-Air-2.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).