public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Gabriel Nützi" <gnuetzi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Proposal: looking for files in `$PWD/filters` etc.
Date: Mon, 17 Aug 2020 15:15:48 +0200	[thread overview]
Message-ID: <e5ae9ccc-9b89-6682-4894-cb55f0cd9dc5@gmail.com> (raw)
In-Reply-To: <1cef908b-f628-ac5c-235f-0311bf9f50df-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

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

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/e5ae9ccc-9b89-6682-4894-cb55f0cd9dc5%40gmail.com.

[-- Attachment #2: Type: text/html, Size: 4365 bytes --]

  parent reply	other threads:[~2020-08-17 13:15 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 [this message]
     [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

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=e5ae9ccc-9b89-6682-4894-cb55f0cd9dc5@gmail.com \
    --to=gnuetzi-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).