public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "Günter Dannoritzer" <dannoritzer-S0/GAf8tV78@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: using panflute to create filters and (hopefully) writers in pandoc
Date: Thu, 07 Jul 2022 00:49:33 +0200	[thread overview]
Message-ID: <m2let5q2ki.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <785dec1b-ea96-4297-9a0e-2d36f9107bddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Lua filters are also much faster, because we avoid the JSON
serialization and deserialization step.  And the Lua API now
exposes many useful functions that you're probably not going
to find in panflute.

Günter Dannoritzer <dannoritzer-S0/GAf8tV78@public.gmane.org> writes:

> I agree with your statement about Python, however, having programmed a few 
> filter for pandoc I struggled with panflute as the core concept to 
> understand is how the pandoc AST works. I did not find that much help in 
> panflute, and it was easier for me to learn lua and use the numerous 
> lua-filter-examples. Also, I find it easier to use lua, as there are no 
> extra installations necessary.
>
> amine.ab...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org schrieb am Dienstag, 5. Juli 2022 um 17:12:42 UTC+2:
>
>> I'd like to avoid using Lua to make my own custom filters, readers and/or 
>> writers and stick to panflute because, well, python is just superior to Lua.
>>
>> If anyone's familiar using panflute, I'd appreciate any commentary or help 
>> I can get on a recent issue 
>> <https://github.com/sergiocorreia/panflute/issues/217> I logged in which 
>> I am trying to process BulletLists.
>>
>> Thanks for your consideration.
>>
>
> -- 
> 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/785dec1b-ea96-4297-9a0e-2d36f9107bddn%40googlegroups.com.

-- 
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/m2let5q2ki.fsf%40johnmacfarlane.net.


  parent reply	other threads:[~2022-07-06 22:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 15:12 A A
     [not found] ` <CAMwawgPtfvK1UC9Tct-ZG7z-TsytK0Cb==GqbpNV0xShfThNtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-05 15:47   ` AW: " denis.maier-NSENcxR/0n0
     [not found]     ` <28435ea53d1845208602828320c543a0-NSENcxR/0n0@public.gmane.org>
2022-07-05 15:59       ` A A
     [not found]         ` <CAMwawgMjYTqrbb4cvZqmSYsEHgNL9C0uiw=c2-7uStuhaeVV6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-05 16:10           ` AW: " denis.maier-NSENcxR/0n0
     [not found]             ` <be10de6788b943e5835cac27b9ec3b0e-NSENcxR/0n0@public.gmane.org>
2022-07-05 16:46               ` Bastien DUMONT
2022-07-06 19:51   ` Günter Dannoritzer
     [not found]     ` <785dec1b-ea96-4297-9a0e-2d36f9107bddn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-06 22:49       ` John MacFarlane [this message]
     [not found]         ` <m2let5q2ki.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-07-07  9:51           ` A A
     [not found]             ` <CAMwawgN9VkZoWgvdw6xLvoLaB3QRUktswSP8VCuPvjmWvM5xsw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-07  9:55               ` Bastien DUMONT
2022-07-07 10:00                 ` A A
2022-07-07 21:58               ` John MacFarlane

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=m2let5q2ki.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=dannoritzer-S0/GAf8tV78@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).