public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: loading files from data-dir paths
Date: Sat, 30 Apr 2022 07:49:55 +0000	[thread overview]
Message-ID: <YmzqI5Gu2PRMt6xF@localhost> (raw)
In-Reply-To: <0c7cd331-4b3a-4569-9dc8-d0da10da0cbcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Did you try to look at the output `pandoc --version` to know where your data directory is?

Le Friday 29 April 2022 à 05:48:47PM, jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org a écrit :
> Hello!
> 
> Excuse me for my insistence, but even in version 1.18 I cannot figure out how
> to make a custom repository of configuration files for groff ms or lua filters
> instead of copying and/or moving them around each working directory. Any
> solution?
> 
> Thanks in advance,
> 
> 
> 
> Il giorno mercoledì 16 febbraio 2022 alle 17:22:11 UTC-6 jlr...@gmail.com ha
> scritto:
> 
>     Hello!
> 
>     I was trying to avoid setting the same metadata on different files, and I
>     read in the manual that yaml metadata are interpreted as markdown if loaded
>     with `--metadata-file`, so that would not fly. So I tried to put them my
>     customizations in different files for each backend (roughly, TeX and ms, to
>     generate PDFs) and load them on the command line as follows
> 
>     $ pandoc -B [1]2c.ms -H [2]wideltr.ms -H [3]es.ms --eol=lf -st ms
>     filename.docx | groff -e -t -ms -Dutf8 | awk '{print > "[4]filename.ps"}'
> 
>     This works if *.ms are in the same working directory, but not if I put them
>     in the data-dir built-in into pandoc's executable. Where should I put them
>     so that I don't have to multiply copies in every working directory? I tried
>     the base directory, and the templates subdirectory, of pandoc's data-dir,
>     where I have my [5]default.ms template. I'm working on Win10, both personal
>     and professional.
> 
>     Cheers!
> 
> 
> 
> --
> 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 [6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [7]https://groups.google.com/d/msgid/
> pandoc-discuss/0c7cd331-4b3a-4569-9dc8-d0da10da0cbcn%40googlegroups.com.
> 
> References:
> 
> [1] http://2c.ms/
> [2] http://wideltr.ms/
> [3] http://es.ms/
> [4] http://filename.ps/
> [5] http://default.ms/
> [6] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [7] https://groups.google.com/d/msgid/pandoc-discuss/0c7cd331-4b3a-4569-9dc8-d0da10da0cbcn%40googlegroups.com?utm_medium=email&utm_source=footer

-- 
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/YmzqI5Gu2PRMt6xF%40localhost.


  parent reply	other threads:[~2022-04-30  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 23:22 jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found] ` <fa6728c9-d218-486d-bb1b-6fa64aa58befn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-04-30  0:48   ` jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found]     ` <0c7cd331-4b3a-4569-9dc8-d0da10da0cbcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-04-30  7:47       ` Bastien DUMONT
2022-04-30  7:49       ` Bastien DUMONT [this message]
2022-04-30 13:15         ` BPJ

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=YmzqI5Gu2PRMt6xF@localhost \
    --to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).