Yes, that's what I do. But I'm always looking for ways to move 
functionality into the yaml, where it is clear and explicit, vs. hidden in 
the makefile. I see now I read the manual wrong: 

--bibliography=*FILE*

Set the bibliography field in the document’s metadata to *FILE*, overriding 
any value set in the metadata, and process citations using pandoc-citeproc. 
(This is equivalent to --metadata bibliography=FILE --filter pandoc-citeproc
.) 

is saying define a variable and then set the file option, NOT define two 
variables in YAML. Got it.

Thanks for your help and all your work on pandoc. I find it extremely 
valuable. 

Steve

On Wednesday, May 2, 2018 at 3:08:16 PM UTC-4, John MacFarlane wrote:
>
>
> My own approach is to use a Makefile which specifies the options 
> I need for each case.  Then I just type 'make' to build my 
> documents, and I don't have to remember the options in the future. 
>
>

-- 
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/3381c6d1-c4e1-4d5e-ad74-c42207d70de4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.