public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Axel Kielhorn <a.kielhorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Pandoc discuss discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Options, extensions, variables : what can be specified in the YAML header of a Markdown file and what has to be on the command line ?
Date: Sun, 29 Sep 2019 08:23:50 +0200	[thread overview]
Message-ID: <F829EA44-5A95-404B-9B05-76FE9ADE965B@gmail.com> (raw)
In-Reply-To: <m2o8z4z3sr.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>


> Am 28.09.2019 um 20:14 schrieb John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>:
> 
> Command-line options can never be set via YAML metadata, in general,
> though in some cases it may seem as if they can.  For example,
> you can specify `toc: true`; but this only works in formats where
> the only thing the `--toc` option has to do is set a `toc`
> template variable.
> 
> Rather than adding a comment to the source with installation
> instructions, I usually use a simple Makefile:
> 
> output.html: input.md
>             pandoc $< -o $@ --my-options-here…

On systems where I don’t have `make` I keep a separate file with the command lines.
Yes, plural, since I usually create HTML for a quick overview and something else for the final version.

Greetings form a Unix guy in Windows land.
Axel

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/F829EA44-5A95-404B-9B05-76FE9ADE965B%40gmail.com.


  parent reply	other threads:[~2019-09-29  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 17:10 Emmanuel Charpentier
     [not found] ` <5ddf18fd-b35f-4bf2-99d0-03ca657adb28-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-28 18:14   ` John MacFarlane
     [not found]     ` <m2o8z4z3sr.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-28 18:38       ` Emmanuel Charpentier
     [not found]         ` <5e3c4113-1162-41fc-b348-8403976b93cb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-29 19:41           ` John MacFarlane
2019-09-29  6:23       ` Axel Kielhorn [this message]
     [not found]         ` <F829EA44-5A95-404B-9B05-76FE9ADE965B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-09-29 18:17           ` BPJ

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=F829EA44-5A95-404B-9B05-76FE9ADE965B@gmail.com \
    --to=a.kielhorn-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).