public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Stephen Mildenhall <stephen.j.mildenhall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: yaml_metadata_block and bibliography
Date: Wed, 2 May 2018 12:40:37 -0700 (PDT)	[thread overview]
Message-ID: <3381c6d1-c4e1-4d5e-ad74-c42207d70de4@googlegroups.com> (raw)
In-Reply-To: <yh480kefityiy5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1528 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 3644 bytes --]

  parent reply	other threads:[~2018-05-02 19:40 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
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 [this message]
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=3381c6d1-c4e1-4d5e-ad74-c42207d70de4@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).