From: ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Lua Filter: Get to parent of current element?
Date: Wed, 10 May 2023 09:59:11 -0700 (PDT) [thread overview]
Message-ID: <eb2115c3-ee11-4f82-bb49-6fd423d9365fn@googlegroups.com> (raw)
In-Reply-To: <87sfc4ql6b.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1769 bytes --]
Great, thanks both of you, I get the idea, will try that.
T.
On Wednesday, May 10, 2023 at 5:08:06 PM UTC+2 Albert Krewinkel wrote:
>
> ThomasH <the...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > is there a way to get to the parent in the Pandoc AST from the
> > current element in a Lua filter?
> > I would like to distinguish treatment of elements depending on their
> > context in the syntax tree, e.g. handle a 'span' element differently
> > if it is a child of a 'cell' element in a table.
>
> This is currently not supported in Lua; panflute (Python) filters do
> enable that though.
>
> What Lua does support though is to change the order in which elements
> are traversed, as well as the option to stop processing of a subtree.
> See https://pandoc.org/lua-filters.html#traversal-order
>
> E.g., to handle all Spans in a table differently you'd use
>
> traverse = 'topdown'
>
> function Table (tbl)
> return tbl:walk(my_filter_for_table_spans), false
> end
>
> function Span (span)
> -- default span processing
> return span
> end
>
> It's a bit of a brain-twister (and can be slower than normal filters)
> but it enables most of the actions that one would otherwise use the
> parent element for.
>
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
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/eb2115c3-ee11-4f82-bb49-6fd423d9365fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2813 bytes --]
prev parent reply other threads:[~2023-05-10 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 13:02 ThomasH
[not found] ` <b4305519-9dbf-4254-a3d7-7b9e1dab9d6en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-10 13:27 ` Bastien DUMONT
2023-05-10 14:57 ` Albert Krewinkel
[not found] ` <87sfc4ql6b.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-10 16:59 ` ThomasH [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=eb2115c3-ee11-4f82-bb49-6fd423d9365fn@googlegroups.com \
--to=therch-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).