From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: using panflute to create filters and (hopefully) writers in pandoc
Date: Thu, 07 Jul 2022 23:58:47 +0200 [thread overview]
Message-ID: <m2ilo8potk.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <CAMwawgN9VkZoWgvdw6xLvoLaB3QRUktswSP8VCuPvjmWvM5xsw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Furthermore what useful functions are you referring to which the Lua API
> exposes and which panflute doesn't?
For example, blocks_to_inlines, make_sections, functions to
manipulate pandoc's mediabag (which contains resources like
images).
But by all means, use panflute if you want to use Python
libraries! panflute is great.
prev parent reply other threads:[~2022-07-07 21:58 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
[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 [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=m2ilo8potk.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=amine.aboufirass-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).