Interpolation in default file paths -- the current output format?

Interpolation in default file paths -- the current output format?

[BPJ]

[-- 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 --]

Re: Interpolation in default file paths -- the current output format?

[John MacFarlane]

You can already interpret arbitrary environment variables,
so you could do:

FORMAT=docx pandoc -t $FORMAT -d defaults

and in defaults.yaml you could have

output-file: output.${FORMAT}
defaults: ${.}/defaults/${FORMAT}.yaml

BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> 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.