public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Lua filter applied to a specific input file
Date: Thu, 14 Jan 2021 22:54:04 +0100	[thread overview]
Message-ID: <87ft332nib.fsf@zeitkraut.de> (raw)
In-Reply-To: <b921eb81-70fe-43c5-aba0-d4b9317c270dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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)?

One possibility would be to match the exact file name. You can do so by
inspecting the `input_files` field of the global variable
`PANDOC_STATE`:

    local input_files = pandoc.List(PANDOC_STATE.input_files)
    if not input_files:includes('my-special-file.md') then
      return {}
    end

    -- rest of the script begins here.

Does that help?

--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2021-01-14 21:54 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 [this message]
2021-01-14 21:57   ` John MacFarlane
     [not found]     ` <m2r1mnfafv.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-01-15  2:29       ` Peter Matulis

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=87ft332nib.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).