public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Russ <info-ckBjHRpK5r9MPTj2movljOTW4wlIGRCZ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: ${HOME} in defaults files
Date: Mon, 23 May 2022 03:09:14 -0700 (PDT)	[thread overview]
Message-ID: <6766afed-d65b-4853-a07c-d4400063f2c9n@googlegroups.com> (raw)
In-Reply-To: <CADAJKhBFO7b=WppbBnS020NJ3CTXh8J+hjR+Dp5U9hA7=dGKuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2542 bytes --]

I am not sure if this would help, but we use `${USERDATA}` e.g.

```yaml
css:
- "${USERDATA}/epub-css.css"

epub-fonts: 
- "${USERDATA}/fonts/fontname-*.ttf"
```
This is the root of your folder with the `defaults` folder/ `defaults.yaml` 
file in it.

We then call Pandoc with `--data-dir` argument if it is not the default 
location and of course your desired defaults file with `--defaults=xxxx`
On Sunday, 22 May 2022 at 21:15:46 UTC+1 BP wrote:

>
>
> Den sön 22 maj 2022 18:28John MacFarlane <j...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:
>
>>
>> I'm pretty sure that the expansion doesn't work for 'defaults:',
>> but I can't now recall whether there was a reason for that.
>> Maybe submit a bug report?
>>
>
> I will, because this breaks my workflow where I use the same top level 
> defaults file on different machines.
>
>
>
>
>> BPJ <mel...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > I forgot to mention the vital points that `${HOME}...` works with `css: 
>> []`
>> > in the same file and that everything works if I use an absolute path in 
>> the
>> > `defaults: []` entry.
>> >
>> > Den lör 21 maj 2022 20:45BPJ <mel...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>> >
>> >> In a defaults file in the current directory I have the lines:
>> >>
>> >> ``````yaml
>> >> defaults:
>> >>   - ${HOME}/style/ling-html2pdf.yaml
>> >> ``````
>> >>
>> >> I'm sure that file exists but pandoc complains and says it doesn't. 
>> Might
>> >> Pandoc's idea of what `${HOME}` expands to differ from the shell's 
>> idea of
>> >> what `$HOME` expands to?
>> >>
>> >>
>> >>
>> >
>> > -- 
>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhC5X%2BsNjQEFX9mHPryV93TRYBenqVZreU%2B3BdVb7-5V7w%40mail.gmail.com
>> .
>>
>

-- 
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/6766afed-d65b-4853-a07c-d4400063f2c9n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4459 bytes --]

      parent reply	other threads:[~2022-05-23 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 18:45 BPJ
     [not found] ` <CADAJKhDe97TrD6dqvZ1Dt0GgSruGT66v+mW08ucY0zYBaTf9Ag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-05-22  9:29   ` BPJ
     [not found]     ` <CADAJKhC5X+sNjQEFX9mHPryV93TRYBenqVZreU+3BdVb7-5V7w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-05-22 16:28       ` John MacFarlane
     [not found]         ` <m2k0adilak.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-05-22 20:15           ` BPJ
     [not found]             ` <CADAJKhBFO7b=WppbBnS020NJ3CTXh8J+hjR+Dp5U9hA7=dGKuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-05-23 10:09               ` Russ [this message]

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=6766afed-d65b-4853-a07c-d4400063f2c9n@googlegroups.com \
    --to=info-ckbjhrpk5r9mptj2movljotw4wligrcz@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).