From: Pranesh Prakash <the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Proposal: looking for files in `$PWD/filters` etc.
Date: Tue, 25 Aug 2020 12:19:33 -0700 (PDT) [thread overview]
Message-ID: <d3980e63-0da3-4f5f-ac37-6e96a9f33731n@googlegroups.com> (raw)
In-Reply-To: <9362dd24-e6e0-38ec-bb0d-29736ed34b9d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2275 bytes --]
I'm sorry, but I hadn't seen this before submitting this to the issue
tracker as an enhancement request:
https://github.com/jgm/pandoc/issues/6635
In that I talk about a different, but somewhat similar problem: searching
for filters within sub-folders, that is: being able to say `pandoc
--lua-filter=wordcount.lua` to be call `$DATADIR/filters/wordcount/wordcount.lua`.
(Just saying `--lua-filter=wordcount` would be even better, since the file
extension is assumed.)
I should probably have started a discussion rather than opening it in the
issue tracker.
On Monday, 17 August, 2020 at 6:53:05 pm UTC+5:30 BP wrote:
> On 2020-08-17 15:15, Gabriel Nützi wrote:
> > Isn't it that you can set:
> >
> > resource-path: ["./filters] See
> >
> https://github.com/gabyx/TechnicalMarkdown/blob/master/convert/pandoc/defaults/pandoc-dirs.yaml
> > BR
>
> Yes, but I still want pandoc to look for filters (and other files) not
> found in or under the current directory in or under the default data
> directory. Sorry if that wasn't as obvious as I thought it was.
>
> >
> > Am 8/17/2020 um 3:00 PM schrieb BPJ:
> >> I’m not sure if I have brought up this before, but in anything but
> >> trivial projects I usually keep filters, templates and now defaults
> >> files in subdirectories of the project directory called — not
> >> surprisingly — `filters`, `templates`, `defaults`. Now for each filter
> >> I list I have to type the relative path `filters/foo.lua`. It would be
> >> nice if Pandoc before looking for filters etc. not found in the
> >> current directory in appropriately named subdirectories of the data
> >> directory looked in the appropriately named subdirectories of the
> >> current directory. What do the devs and others think about this?
> >>
> >>
> >> /bpj
> >>
> >
>
>
--
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/d3980e63-0da3-4f5f-ac37-6e96a9f33731n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3382 bytes --]
prev parent reply other threads:[~2020-08-25 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 13:00 BPJ
[not found] ` <1cef908b-f628-ac5c-235f-0311bf9f50df-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-17 13:06 ` Leonard Rosenthol
2020-08-17 13:15 ` Gabriel Nützi
[not found] ` <e5ae9ccc-9b89-6682-4894-cb55f0cd9dc5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-17 13:22 ` Benct Philip Jonsson
[not found] ` <9362dd24-e6e0-38ec-bb0d-29736ed34b9d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-25 19:19 ` Pranesh Prakash [this message]
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=d3980e63-0da3-4f5f-ac37-6e96a9f33731n@googlegroups.com \
--to=the.solipsist-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).