* --bibliography and --resource-path @ 2020-12-09 10:30 Stefan Björk [not found] ` <0d7c7a88-b3e6-4bb3-9a29-2f086bec58fen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Stefan Björk @ 2020-12-09 10:30 UTC (permalink / raw) To: pandoc-discuss [-- Attachment #1.1: Type: text/plain, Size: 121 bytes --] Is it me, or are files specified with --bibliography not searched for in the directories specified by --resource-path? ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <0d7c7a88-b3e6-4bb3-9a29-2f086bec58fen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: --bibliography and --resource-path [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> 0 siblings, 1 reply; 4+ messages in thread From: John MacFarlane @ 2020-12-09 18:27 UTC (permalink / raw) To: Stefan Björk, pandoc-discuss Stefan Björk <stefan.bjork-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > Is it me, or are files specified with --bibliography not searched for in > the directories specified by --resource-path? 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. -- 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/m25z5aygv3.fsf%40MacBook-Pro.hsd1.ca.comcast.net. ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <m25z5aygv3.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>]
* Re: --bibliography and --resource-path [not found] ` <m25z5aygv3.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org> @ 2020-12-09 19:49 ` Stefan Björk [not found] ` <427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Stefan Björk @ 2020-12-09 19:49 UTC (permalink / raw) To: pandoc-discuss [-- 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 --] ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: --bibliography and --resource-path [not found] ` <427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2020-12-09 20:57 ` John MacFarlane 0 siblings, 0 replies; 4+ messages in thread From: John MacFarlane @ 2020-12-09 20:57 UTC (permalink / raw) To: Stefan Björk, pandoc-discuss Stefan Björk <stefan.bjork-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: >> >> 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. Created an issue: https://github.com/jgm/pandoc/issues/6940 > 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. For related issues concerning defaults files see https://github.com/jgm/pandoc/issues/6108 https://github.com/jgm/pandoc/issues/5982 -- 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/m2a6umwvdj.fsf%40MacBook-Pro.hsd1.ca.comcast.net. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-12-09 20:57 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-12-09 10:30 --bibliography and --resource-path 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 [not found] ` <427f9d5b-82cd-4da9-a6d4-3c09ae4023ddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2020-12-09 20:57 ` John MacFarlane
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).