public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: loading files from data-dir paths
Date: Wed, 16 Feb 2022 15:22:10 -0800 (PST)	[thread overview]
Message-ID: <fa6728c9-d218-486d-bb1b-6fa64aa58befn@googlegroups.com> (raw)


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

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 2c.ms -H wideltr.ms -H es.ms --eol=lf -st ms filename.docx | 
groff -e -t -ms -Dutf8 | awk '{print > "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 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 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/fa6728c9-d218-486d-bb1b-6fa64aa58befn%40googlegroups.com.

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

             reply	other threads:[~2022-02-16 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 23:22 jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
     [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
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=fa6728c9-d218-486d-bb1b-6fa64aa58befn@googlegroups.com \
    --to=jlrn77-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).