From: Peter Matulis <pmatulis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Lua filter applied to a specific input file
Date: Thu, 14 Jan 2021 21:29:19 -0500 [thread overview]
Message-ID: <CAMxYqzGdmf05ObLdWrbwb=Cdswtk_bELij2G8Ed0ewX5M1Ypvw@mail.gmail.com> (raw)
In-Reply-To: <m2r1mnfafv.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]
Awesome. Thank you both.
On Thu, 14 Jan 2021 at 16:58, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
>
> PANDOC_STATE.input_files should give you an array of the input
> files in the filter.
>
> Peter <pmatulis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > I have a working Lua filter and I'll be having pandoc iterate over
> multiple
> > input files (for loop). However, I know in advance that my filter will
> only
> > match on a specific file's data. Is it possible, within the AST model,
> to
> > have the filter bail unless it's inspecting data associated with this
> > specific file? Or do I need to deal with this at the pandoc invocation
> > level (i.e. specify what filter to use based on the input files)?
> >
> > --
> > 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/b921eb81-70fe-43c5-aba0-d4b9317c270dn%40googlegroups.com
> .
>
--
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/CAMxYqzGdmf05ObLdWrbwb%3DCdswtk_bELij2G8Ed0ewX5M1Ypvw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2700 bytes --]
prev parent reply other threads:[~2021-01-15 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 21:18 Peter
[not found] ` <b921eb81-70fe-43c5-aba0-d4b9317c270dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-01-14 21:54 ` Albert Krewinkel
2021-01-14 21:57 ` John MacFarlane
[not found] ` <m2r1mnfafv.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-01-15 2:29 ` Peter Matulis [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='CAMxYqzGdmf05ObLdWrbwb=Cdswtk_bELij2G8Ed0ewX5M1Ypvw@mail.gmail.com' \
--to=pmatulis-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).