From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Stephen Mildenhall
<stephen.j.mildenhall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: yaml_metadata_block and bibliography
Date: Wed, 02 May 2018 12:07:13 -0700 [thread overview]
Message-ID: <yh480kh8npyizi.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <fbea6c6e-f31b-4047-9c96-82f30bfeef2e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Metadata sets variables. But it doesn't affect command-line
options in general. There are a number of issues on the tracker
requesting some general way to do this.
Stephen Mildenhall <stephen.j.mildenhall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Thanks. But you can't specify to run citeproc in the yaml with filter:
> pandoc-citeproc. Is there some reason that option doesn't pass through?
>
>
> On Wednesday, May 2, 2018 at 1:48:01 PM UTC-4, John MacFarlane wrote:
>>
>>
>> Yes, you can indicate the bibliography in a YAML metadata block.
>>
>> Note, however, that you need to tell pandoc explicitly to
>> use the pandoc-citeproc filter
>>
>> --filter pandoc-citeproc
>>
>> For backwards compatibility, it does this automatically when
>> you specify --bibliography on the command line. But not when
>> you have this in YAML metadata.
>>
>> Stephen Mildenhall <stephen.j....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes:
>>
>> > 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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
>> > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>> <javascript:>.
>> > 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.
>>
>
> --
> 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/fbea6c6e-f31b-4047-9c96-82f30bfeef2e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2018-05-02 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 14:57 Stephen Mildenhall
[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 [this message]
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=yh480kh8npyizi.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=stephen.j.mildenhall-Re5JQEeQqe8AvxtiuMwx3w@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).