From: Bruno Grenet <bruno.grenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Slide level in lua filters
Date: Thu, 12 Jan 2023 06:29:40 -0800 (PST) [thread overview]
Message-ID: <5716cb0a-c39c-4bf4-9449-cfd4aa06aeffn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]
Hi,
Is it possible to access the *computed* slide level from a lua filter?
I know that one can access to the slide-level command line option, though
it is not always explicitly provided. In that case, the writers (? not
sure) determine a slide-level by some rule. My question is whether this
slide level can be used inside a lua filter.
For my use case, other possibilities may exist. Indeed, I am creating
Beamer slides from markdown. What I'd really like to access is the
"(beamer) block level": That is, headers with a level lower than the slide
level are converted to beamer blocks in the LaTeX writer. I'd like to be
able to apply a filter on these beamer blocks. This corresponds to applying
a filter to headers of a certain level, determined with respect to the
slide level. It may be possible to achieve what I want with a custom
writer, but I would prefer to stick to filters that I am more familiar with.
Thanks,
Bruno
--
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/5716cb0a-c39c-4bf4-9449-cfd4aa06aeffn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1762 bytes --]
next reply other threads:[~2023-01-12 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 14:29 Bruno Grenet [this message]
[not found] ` <5716cb0a-c39c-4bf4-9449-cfd4aa06aeffn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-12 19:18 ` Albert Krewinkel
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=5716cb0a-c39c-4bf4-9449-cfd4aa06aeffn@googlegroups.com \
--to=bruno.grenet-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).