From: jcr <ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Identifying a Header
Date: Tue, 31 Jan 2023 08:43:59 -0800 (PST) [thread overview]
Message-ID: <e3c3ed37-ba0e-4525-85ef-fa43c7f2e2den@googlegroups.com> (raw)
In-Reply-To: <CAEe_xxjG-oAvWUpPnL3t0TiBtiDWmaKEoH+R+PVX3iPtJBG+Jw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1570 bytes --]
Thank you. I was about to resort to duck typing, since Header is the only
element that has level (besides Chunk).
On Tuesday, January 31, 2023 at 11:39:05 AM UTC-5
wlu...-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org wrote:
> Use .tag or .t (ref. https://pandoc.org/lua-filters.html#type-header).
>
> On Tue, 31 Jan 2023 at 16:07, jcr <ffi.a...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> How do I test whether a block is a Header? pandoc.utils.type(el) just
>> returns "Block" for Header, Div, Para, etc.
>>
>> I'm still using pandoc 2.19.2, if it matters.
>>
>> --
>> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pandoc-discuss/f319694d-073d-4c4d-b447-681f3d4c21bcn%40googlegroups.com
>> <https://groups.google.com/d/msgid/pandoc-discuss/f319694d-073d-4c4d-b447-681f3d4c21bcn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
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/e3c3ed37-ba0e-4525-85ef-fa43c7f2e2den%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3270 bytes --]
prev parent reply other threads:[~2023-01-31 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 16:07 jcr
[not found] ` <f319694d-073d-4c4d-b447-681f3d4c21bcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-31 16:38 ` 'William Lupton' via pandoc-discuss
[not found] ` <CAEe_xxjG-oAvWUpPnL3t0TiBtiDWmaKEoH+R+PVX3iPtJBG+Jw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-01-31 16:43 ` jcr [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=e3c3ed37-ba0e-4525-85ef-fa43c7f2e2den@googlegroups.com \
--to=ffi.appdev-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).