public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: RFC: compiling lpeg into pandoc
Date: Mon, 01 Nov 2021 14:38:09 +0100	[thread overview]
Message-ID: <87ee806loe.fsf@zeitkraut.de> (raw)

Hi all,

I'd like to request views and opinions on the inclusion of a Lua library
into pandoc: the LPeg library is a small parsing library written in C to
be used with Lua. http://www.inf.puc-rio.br/~roberto/lpeg/

The motivation is that this library could be used to extend pandoc to
deal with new formats. A good example is jgm's "lunamark", which could
be modified to support custom syntax extensions that might otherwise be
difficult to implement with current filters.
https://github.com/jgm/lunamark/blob/master/lunamark/reader/markdown.lua

On the other hand, this is yet another library and could be considered
bloat. Most users, esp. on Mac and Linux, should not find it too
difficult to install the library on their system should they need it.

The question is therefore if you think whether including lpeg into
pandoc would make is worth it; e.g., do you believe you'd write such
LPeg-based parsers? Would you share them with people who wouldn't
immediately know how to install the library themselves?

Thanks in advance,
Albert


PS: The corresponding pull request is
    https://github.com/jgm/pandoc/pull/7649

--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


             reply	other threads:[~2021-11-01 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 13:38 Albert Krewinkel [this message]
     [not found] ` <87ee806loe.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-11-01 22:06   ` AW: " denis.maier-NSENcxR/0n0
     [not found]     ` <83dbc2c6dcbe49e49e00dac40b73eb65-NSENcxR/0n0@public.gmane.org>
2021-11-02 11:44       ` denis.maier-NSENcxR/0n0
     [not found]         ` <ec915ee445b6471fb1f252d98a727e3d-NSENcxR/0n0@public.gmane.org>
2021-11-02 11:52           ` Albert Krewinkel
     [not found]             ` <878ry67p0o.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-11-02 12:38               ` BPJ
2021-11-02 13:28               ` AW: " denis.maier-NSENcxR/0n0
     [not found]                 ` <a4454aeb346b404ba248ee962bacd7cd-NSENcxR/0n0@public.gmane.org>
2021-11-02 13:37                   ` BPJ
     [not found]                     ` <CADAJKhD=XdoUF6cg06uNqdGRXW1tdOzidv82=m84n9gSHR-LjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-11-03  9:41                       ` krulis....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2021-11-01 23:14   ` RFC: " BPJ
2021-11-08 15:38   ` 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=87ee806loe.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).