From: "Stefan Björk" <stefan.bjork-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: --bibliography and --resource-path
Date: Wed, 9 Dec 2020 11:49:05 -0800 (PST) [thread overview]
Message-ID: <427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn@googlegroups.com> (raw)
In-Reply-To: <m25z5aygv3.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1093 bytes --]
>
> Correct, currently they are not.
> This could be changed, I suppose.
> If we used fetchItem instead of readFileStrict, then we'd get
> both (a) searching of resource paths and (b) the ability
> to specify bibliographies at URLs.
>
Sounds like a good idea to me.
A related question regarding paths: for someone like me that use pandoc on
different systems with different home directories, it would be wonderful if
'~' or '$HOME' or something similar in YAML blocks could be expanded to the
home directory. Or some other way of specifying paths relative to the home
directory. That way, I could use the exact same configuration files on all
systems.
.:: Stefan ::.
--
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/427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1623 bytes --]
next prev parent reply other threads:[~2020-12-09 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 10:30 Stefan Björk
[not found] ` <0d7c7a88-b3e6-4bb3-9a29-2f086bec58fen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-09 18:27 ` John MacFarlane
[not found] ` <m25z5aygv3.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-12-09 19:49 ` Stefan Björk [this message]
[not found] ` <427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-09 20:57 ` John MacFarlane
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=427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn@googlegroups.com \
--to=stefan.bjork-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).