From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc 2.18 - Custom writer working example
Date: Thu, 02 Jun 2022 10:43:00 +0200 [thread overview]
Message-ID: <87bkvb5tay.fsf@zeitkraut.de> (raw)
In-Reply-To: <cde6d369-8813-41ed-a1ea-253901014b46n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Hi Felix,
Felix SOEDJEDE <soefelix-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> 1/ Writer
> Using --to=sample.lua works when --standalone is not present and .
> Otherwise I have this error: Could not find data file
> templates/default.sample.lua
Ah, right. With `--standalone` pandoc is looking for a template that
matches the writer name. There isn't one of course. Just omit it.
> Using --writer=sample.lua does not work.
> Error: "Unknown option --writer."
Whoops, should have been `--write`. I'm cutting down on coffee, I guess
it shows. 😬
> 2/ Accessing variables in lua filter
> I would like to have access to "variables" in lua filter.
If you use `function Writer(doc, opts)`, then the variables are
available via `opts.variables`.
> I prefer not to use "function Writer" for now if possible.
> Do you have any tips or working examples for that one?
Do you mean an example of a classic custom writers? Pandoc has an
example built-in, it's available via
pandoc --print-default-data-file=sample.lua
Classic writers are generally a bit easier (IMHO). I'd recommend new-
style writers if you either base the new writer on one that's already
included in pandoc, or if you want to make use of the `pandoc.layout`
module to get nicer looking output. Other than those cases, classic
writers are frequently the better choice.
Out of curiosity, what output format are planning to generate?
Cheers,
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/87bkvb5tay.fsf%40zeitkraut.de.
next prev parent reply other threads:[~2022-06-02 8:43 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 [this message]
[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
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=87bkvb5tay.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).