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: Get to parent of current element?
Date: Wed, 10 May 2023 16:57:19 +0200	[thread overview]
Message-ID: <87sfc4ql6b.fsf@zeitkraut.de> (raw)
In-Reply-To: <b4305519-9dbf-4254-a3d7-7b9e1dab9d6en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


ThomasH <therch-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


  parent reply	other threads:[~2023-05-10 14:57 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 [this message]
     [not found]     ` <87sfc4ql6b.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-10 16:59       ` ThomasH

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=87sfc4ql6b.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).