From: Felix SOEDJEDE <soefelix-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc 2.18 - Custom writer working example
Date: Fri, 3 Jun 2022 00:31:18 -0700 (PDT) [thread overview]
Message-ID: <35a61b60-d763-4d60-a545-cd5329f65883n@googlegroups.com> (raw)
In-Reply-To: <87tu933tb0.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1383 bytes --]
Well that was easier than I thought.
I did not try that. My bad 🤦🏽♂️.
It's all good now
Have a nice day
Le jeudi 2 juin 2022 à 18:48:43 UTC+2, Albert Krewinkel a écrit :
>
> Felix SOEDJEDE <soef...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > My real need is that I want to be able to access variables in my lua
> > filters.
>
> In that case there might be a simpler solution: The global
> PANDOC_WRITER_OPTIONS became available in pandoc 2.17. With that you can
> access variables in writers by indexing
> `PANDOC_WRITER_OPTIONS.variables`.
>
> To give a short example: if you call pandoc with
>
> pandoc --lua-filter=var-test.lua --variable foo=hello <<< ''
>
> where `var-test.lua` contains
>
> print(PANDOC_WRITER_OPTIONS.variables.foo)
>
> then you'll get `hello` printed to the terminal.
>
> HTH,
> Albert
>
>
> --
> 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/35a61b60-d763-4d60-a545-cd5329f65883n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2078 bytes --]
prev parent reply other threads:[~2022-06-03 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 23:01 Felix SOEDJEDE
[not found] ` <8528d41a-d6dd-4ca7-b38a-13955a9d1eabn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-02 5:27 ` Albert Krewinkel
[not found] ` <87fskn6345.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-02 8:10 ` Felix SOEDJEDE
[not found] ` <cde6d369-8813-41ed-a1ea-253901014b46n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-02 8:43 ` Albert Krewinkel
[not found] ` <87bkvb5tay.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-02 14:40 ` Felix SOEDJEDE
[not found] ` <56920de7-922c-4491-86ee-c981beb37b78n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-02 16:40 ` Albert Krewinkel
[not found] ` <87tu933tb0.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-03 7:31 ` Felix SOEDJEDE [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=35a61b60-d763-4d60-a545-cd5329f65883n@googlegroups.com \
--to=soefelix-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).