From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Lua: pandoc.read() with current reader options
Date: Sat, 6 May 2023 16:51:26 +0200 [thread overview]
Message-ID: <CADAJKhC02NbUxS8Unumv58qTdoKHn8H7=g=0z4iKvZLvMccq_w@mail.gmail.com> (raw)
In-Reply-To: <87mt58df5s.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
Is there any way to get the current input format in Lua?
Den mån 20 feb. 2023 07:29Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
skrev:
>
> BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > This one is for Albert I guess.
> >
> > Is it now possible to invoke `pandoc.read()` inside a filter and
> > apply the reader options from the current invocation of `pandoc`? If
> > so how?
>
> local flavor = {
> format = 'markdown',
> extensions = PANDOC_READER_OPTIONS.extensions
> }
>
> function CodeBlock (cb)
> return pandoc.read(cb.text, flavor, PANDOC_READER_OPTIONS).blocks
> end
>
> With that, everything in code block will be parsed in exactly the same
> way as the main input.
>
> Cheers!
>
>
> --
> 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/87mt58df5s.fsf%40zeitkraut.de
> .
>
--
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/CADAJKhC02NbUxS8Unumv58qTdoKHn8H7%3Dg%3D0z4iKvZLvMccq_w%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2768 bytes --]
prev parent reply other threads:[~2023-05-06 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 13:11 BPJ
[not found] ` <CADAJKhAcGpKWDNFU85hauzRLF+Y-n2T-PyAnE6L8YSvJbJYqyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-02-20 6:24 ` Albert Krewinkel
[not found] ` <87mt58df5s.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-06 14:51 ` BPJ [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='CADAJKhC02NbUxS8Unumv58qTdoKHn8H7=g=0z4iKvZLvMccq_w@mail.gmail.com' \
--to=melroch-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).