From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Interpolation in default file paths -- the current output format?
Date: Tue, 1 Jun 2021 10:56:32 +0200 [thread overview]
Message-ID: <CADAJKhB3zWPC_601kJYNjFO7_y2+xK1M7x_YG6AvJnRDe_BrGw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
I have been thinking about the feature with `${HOME}` etc. in default file
paths. It would be good to also have `${OUTPUTFORMAT}` (or just `${FORMAT}`
like the Lua variable) so that you could do things like this:
``````yaml
defaults:
- ${.}/defaults/${FORMAT}.yaml
``````
Filters, CSS, includes and metadata/variables come to mind as things which
often should be different based on the output format in a single-source
scenario which could be handled this way, but there probably would be other
uses which at least I can't foresee.
While there certainly are situations where you could invert this and say
``````yaml
defaults:
- ${.}/defaults/common.yaml
``````
in `./defaults/latex.yaml` there certainly are situations where including
the format-specific file from the common file will be more intuitive.
/bpj
--
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/CADAJKhB3zWPC_601kJYNjFO7_y2%2BxK1M7x_YG6AvJnRDe_BrGw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2000 bytes --]
next reply other threads:[~2021-06-01 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:56 BPJ [this message]
[not found] ` <CADAJKhB3zWPC_601kJYNjFO7_y2+xK1M7x_YG6AvJnRDe_BrGw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-01 20:06 ` 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=CADAJKhB3zWPC_601kJYNjFO7_y2+xK1M7x_YG6AvJnRDe_BrGw@mail.gmail.com \
--to=melroch-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).