public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to overwrite values from default file in the document
Date: Sun, 21 May 2023 16:19:07 +0200	[thread overview]
Message-ID: <877ct1sqx0.fsf@zeitkraut.de> (raw)
In-Reply-To: <e8781103-e0b6-4194-975b-960965ac0e91n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Oliver Baumann <news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org> writes:

> Hi there, I am using Defaults files to give my documents a standard
> look. This works absolutely fantastic.
> However sometimes I want to overwrite settings from the Defaults file
> in the document YAML block, but this doesn't always work.

The defaults files should be thought of defining default values for
*command line arguments*. This is important in this context, because
metadata values given on the command line will always override those
defined in the document. That means that metadata defined in a defaults
file can only be overridden via command line options, not via values in
the document.

Instead, you may want to use `--metadata-file`, which can be thought of
a defaults file for metadata, as those values _can_ be overridden by the
YAML in the document itself.


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2023-05-21 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21  8:05 Oliver Baumann
     [not found] ` <e8781103-e0b6-4194-975b-960965ac0e91n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-21 14:19   ` Albert Krewinkel [this message]
     [not found]     ` <877ct1sqx0.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-22  4:14       ` oliver

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=877ct1sqx0.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).