From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Access input format in Lua filter
Date: Fri, 16 Jun 2023 19:13:40 +0200 [thread overview]
Message-ID: <CADAJKhBKc1zzomBR46Rd3-n-ds_q3QAmU0gaX=sw8sRig0PfAg@mail.gmail.com> (raw)
In-Reply-To: <086e28fb-4818-462d-bda2-6b15d0fb8710n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
Den fre 16 juni 2023 16:30Bernardo C. D. A. Vasconcelos <
bernardovasconcelos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
> I think it is the constant FORMAT, but I could be mistaken.
>
That is the output format. I need the input format.
> On Friday, June 16, 2023 at 8:33:12 AM UTC-3 BPJ wrote:
>
>> Is there any way to get the current input format in a Lua filter?
>>
>> I asked this a while back in another thread but got no answer, so I ask
>> again in a dedicated thread. Apologies if there was an answer and I missed
>> it!
>>
> --
> 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/086e28fb-4818-462d-bda2-6b15d0fb8710n%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/086e28fb-4818-462d-bda2-6b15d0fb8710n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/CADAJKhBKc1zzomBR46Rd3-n-ds_q3QAmU0gaX%3Dsw8sRig0PfAg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2831 bytes --]
prev parent reply other threads:[~2023-06-16 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 11:32 BPJ
[not found] ` <CADAJKhCS6vLYNC+oc597jo_51OSBzdMNu3Es=LGZGpgvQ0xx7Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-16 14:29 ` Bernardo C. D. A. Vasconcelos
[not found] ` <086e28fb-4818-462d-bda2-6b15d0fb8710n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-16 17:13 ` 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='CADAJKhBKc1zzomBR46Rd3-n-ds_q3QAmU0gaX=sw8sRig0PfAg@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).