public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Lua Filter: Detect Type of Inlines
Date: Sat, 13 May 2023 02:00:16 -0700 (PDT)	[thread overview]
Message-ID: <f31b8b9b-f30e-45c6-91d5-caddb494f5b0n@googlegroups.com> (raw)
In-Reply-To: <87o7mpqwfd.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1912 bytes --]

Great, thanks.

On Friday, May 12, 2023 at 7:41:50 PM UTC+2 Albert Krewinkel wrote:

>
> ThomasH <the...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > I want to detect the types of the inline elements of a paragraph. I
> > understand there is pandoc.utils.type() that basically does that, but
> > when I run
> >
> > function Para(para)
> >     for i = 1,#para.content,1 do
> >         print(tostring(pandoc.utils.type(para.content[i])))
> >     end
> > end
> >
> > all that is printed is "Inline" for all elements, not specific types
> > like Str, Span, Link or Image. How can I get at the specific types?
>
> The trick here is that we are using Haskell terminology: Inline is a
> *type*, and Str, Span, Link, etc. are *constructors* for this type. In
> Lua (and JSON) contexts, the property that identifies the name of the
> constructor of a value is called a "tag". Try this:
>
> ``` lua
> function Para(para)
> for i = 1,#para.content do
> print(para.content[i].tag))
> end
> end
> ```
>
> The `.t` property is an alias for `.tag` and can be used as well.
>
> I have plans to change the behavior of `pandoc.utils.type` and to make
> the function return two results. The first result would stay as-is, with
> the second result containing the constructor name. But I need to run
> more tests to ensure that this won't lead to performance degradation.
>
>
> -- 
> 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/f31b8b9b-f30e-45c6-91d5-caddb494f5b0n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2623 bytes --]

  parent reply	other threads:[~2023-05-13  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 17:13 ThomasH
     [not found] ` <4d901ab9-179d-4274-8ce9-fdf36056905fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-12 17:32   ` Albert Krewinkel
     [not found]     ` <87o7mpqwfd.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-13  9:00       ` ThomasH [this message]
     [not found]         ` <f31b8b9b-f30e-45c6-91d5-caddb494f5b0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-13 10:56           ` 'William Lupton' via pandoc-discuss

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=f31b8b9b-f30e-45c6-91d5-caddb494f5b0n@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).