public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Thomas Hodgson <thomas.hodgson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Bibliography in data dir
Date: Fri, 24 Nov 2023 08:19:42 -0800 (PST)	[thread overview]
Message-ID: <1ea63e0e-ac12-4908-bc40-ba745732dd57n@googlegroups.com> (raw)


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

Templates, csl files, metadata files, and defaults can be stored in 
directories inside Pandoc's data dir. I find myself wanting to do something 
similar with bibliographies. Is there a reason why Pandoc doesn't support 
that?

I seem to recall that when the data dir was '~/.pandoc' (on Linux) this 
would work.

(Looking this up in the manual has also made me wonder what the difference 
is between saying that, e.g., `--template` takes 'FILE|URL' and, e.g., 
`--bibliography` and `--csl` take a FILE, which can be a URL. Do some 
things that take FILE not allow it to be a URL? For example, neither 
`--defaults` nor `--metadata-file` mention a URL. Also, some of these flags 
look in the resource path, before the data dir, and some don't, at least 
according to the manual.)

-- 
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/1ea63e0e-ac12-4908-bc40-ba745732dd57n%40googlegroups.com.

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

                 reply	other threads:[~2023-11-24 16:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1ea63e0e-ac12-4908-bc40-ba745732dd57n@googlegroups.com \
    --to=thomas.hodgson-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).