From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Detectiing footnotes in Lua scripts
Date: Mon, 13 Dec 2021 21:20:26 +0100 [thread overview]
Message-ID: <87ee6gnto5.fsf@zeitkraut.de> (raw)
In-Reply-To: <F8CB6356-E282-40D0-BCB6-36D0C8FAAF1C-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org writes:
> Looking at the PR, I spotted a typo on line 233 of doc/lua-filter.md:
> "be" should be deleted from "will be try the following filter
> functions".
Thanks, fixed.
> I see that the documentation only illustrates how to not traverse
> footnotes. Should it also illustrate how to apply a separate filter?
> The walk() method is new to me.
Indeed, it *is* new. The `walk` methods are basically more convenient
variants of `pandoc.utils.walk_inline` and `pandoc.utils.walk_block`,
but are now available on Pandoc, Block, and Inline objects, as well as
on lists of blocks (Blocks) and lists of inlines (Inlines). The method
is documented in each of these types; here it is for Block values:
https://github.com/jgm/pandoc/blob/master/doc/lua-filters.md?plain=1#L916-L947
Examples using `walk` will include
<https://github.com/jgm/pandoc/blob/master/doc/lua-filters.md#counting-words-in-a-document>
and
<https://github.com/jgm/pandoc/blob/master/doc/lua-filters.md#modifying-pandocs-manualtxt-for-man-pages>
A good example to demo its use in combination with `traverse =
'topdown'` could be helpful.
prev parent reply other threads:[~2021-12-13 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 9:49 jcr
[not found] ` <111b665a-1b7a-4856-bf37-d96780a07c24n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-11-24 17:59 ` John MacFarlane
[not found] ` <m2y25dtoxb.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-11-25 19:02 ` FI Apps
[not found] ` <F6A8DF67-F34E-4FF9-A7A2-CF451E96D683-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-11-30 20:50 ` BPJ
[not found] ` <CADAJKhByRxPwZOqgkfkV6ZoSFfBZhHHX52mpyB36_ShLR40Gyg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-12-02 18:58 ` ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w
2021-12-13 17:15 ` Albert Krewinkel
[not found] ` <87fsqwo28w.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-12-13 19:08 ` ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <F8CB6356-E282-40D0-BCB6-36D0C8FAAF1C-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-12-13 20:20 ` Albert Krewinkel [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=87ee6gnto5.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).