From: Stephen Mildenhall <stephen.j.mildenhall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: yaml_metadata_block and bibliography
Date: Wed, 2 May 2018 07:57:03 -0700 (PDT) [thread overview]
Message-ID: <856c6edc-e70f-4e0c-9387-29c399679b28@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1459 bytes --]
My understanding is I can specify variables in yaml and use the
yaml_metadata_block extension to pass them as metadata key value pairs to
pandoc. Thus if my input file is:
---
bibliography: somefile.bib
---
Content and @references
and I run
>> pandoc -f markdown+yaml_metadata_block [other options]
I should get the same result as
>> pandoc -f markdown -M bibliography=somefile.bib [...]
and the same as
>> pandoc -f markdown -bibliography=somefile.bib.
The last two versions, where I pass the biblio filename explicitly, work as
expected. But going through the yaml block and using the extension does
not. The csl= options is also ignored. But link-citations: true works from
yaml when I use the explicit version.
What am I missing?
Being able to control everything from the yaml would be fantastically
helpful....so I hope there is a solution.
Thanks!
Steve
--
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/856c6edc-e70f-4e0c-9387-29c399679b28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2251 bytes --]
next reply other threads:[~2018-05-02 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 14:57 Stephen Mildenhall [this message]
[not found] ` <856c6edc-e70f-4e0c-9387-29c399679b28-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-05-02 17:47 ` John MacFarlane
[not found] ` <yh480kfu3aymot.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-05-02 18:28 ` Stephen Mildenhall
[not found] ` <fbea6c6e-f31b-4047-9c96-82f30bfeef2e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-05-02 19:07 ` John MacFarlane
2018-05-02 22:50 ` msprevak
2018-05-02 19:08 ` John MacFarlane
[not found] ` <yh480kefityiy5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-05-02 19:40 ` Stephen Mildenhall
2018-05-04 8:17 ` J
[not found] ` <90202344-2943-4d7d-942c-4b6726153b46-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-05-05 16:55 ` John MacFarlane
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=856c6edc-e70f-4e0c-9387-29c399679b28@googlegroups.com \
--to=stephen.j.mildenhall-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).