From: Christopher Grieser <grieser.chris-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Is it possible to overide CLI options with YAML (instead of the other way round)??
Date: Thu, 12 Aug 2021 04:31:25 -0700 (PDT) [thread overview]
Message-ID: <a634a37f-a569-41de-8fad-398fd3eb32e3n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1732 bytes --]
Hi everyone,
I am new to this Forum – if this is the wrong place for this kind of
question, I apologize; feel free to point me to the right place then.
My question: When there are conflictings between YAML-Metadata and CLI
options, the standard behavior of Pandoc is a) to extend the information
(e.g. with --include-in-header) in some cases when it is repeatable, or to
override the YAML-Metadata with the CLI options (e.g. --csl or
--bibliography).
Is it somehow possible to control the behavior more precisely? For example:
1. in conflicting cases, YAML-Metadata overrides CLI options
2. in repeatable cases, extend the CLI options with the YAML Metadata.
Option 1 could be useful for the --csl option, when you want to prevent the
use of a different citation style, when a different user compiles the
document with a different csl. Option 2 could be useful for --bibliography
to "add" document-specific citations while you use your main bibliography
via CLI. (especially the later strikes me as unusual, since with some other
repeatable options, the YAML-Metadata is extended and not overridden.)
More generally, I am wondering whether there is/could be something like an
"--yaml-overrides-cli=[true/false]" option to control this behavior?
Best,
Chris
--
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/a634a37f-a569-41de-8fad-398fd3eb32e3n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2181 bytes --]
next reply other threads:[~2021-08-12 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 11:31 Christopher Grieser [this message]
[not found] ` <a634a37f-a569-41de-8fad-398fd3eb32e3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-12 17:30 ` John MacFarlane
[not found] ` <m24kbufu4t.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-08-12 18:09 ` Christopher Grieser
[not found] ` <f95177a3-19cd-46f4-8228-cf33898723d9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-12 18:15 ` Daniel Staal
[not found] ` <a649c458-6981-c0de-5c69-b6cf15b76693-Jdbf3xiKgS8@public.gmane.org>
2021-08-12 18:25 ` Christopher Grieser
[not found] ` <9378266b-ebeb-40e0-8878-f8e606981ee9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-13 21:13 ` Daniel Staal
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=a634a37f-a569-41de-8fad-398fd3eb32e3n@googlegroups.com \
--to=grieser.chris-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).