public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
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: Thu, 2 Jun 2022 01:10:55 -0700 (PDT)	[thread overview]
Message-ID: <cde6d369-8813-41ed-a1ea-253901014b46n@googlegroups.com> (raw)
In-Reply-To: <87fskn6345.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2258 bytes --]

@Albert

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*

Using *--writer=sample.lua* does not work. 
Error: "Unknown option --writer."

I now know why using "--to" did not work.

2/ Accessing variables in lua filter
I would like to have access to "variables" in lua filter.
Currently I have access to "metadata" when I use "*function Pandoc(doc) ... 
end*"
In the doc: https://pandoc.org/custom-writers.html#a-custom-html-writer, I 
saw this "*function Doc(body, meta, vars) ... end*" but it's never called 
in my tests.
I prefer not to use "*function Writer*" for now if possible.
Do you have any tips or working examples for that one?

Thanks

Le jeudi 2 juin 2022 à 07:33:54 UTC+2, Albert Krewinkel a écrit :

>
> Felix SOEDJEDE <soef...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > In Pandoc 2.18, custom writers were added:
> > https://pandoc.org/custom-writers.html#new-style
> >
> > I tried to use it but it's not working and I don't know if it's an
> > error or I'm using it the wrong way.
> >
> > [...]
> >
> > Command used "pandoc --standalone --verbose --lua-filter=sample.lua
> > --output=output.md sample.md"
>
> Pandoc expects the custom writer to be given as the argument of
> `-t`/`--to`/`-w`/`--write`.
>
> pandoc --standalone --verbose --to=sample.lua ...
>
> > Does anyone have a minimal working example for "Doc" or "Writer" I
> > could use?
>
> Here's a custom Markdown writer. It's an experiment designed to show how
> a new writer might be structured. It's a bit slow though.
> https://gist.github.com/tarleb/5a9c3fbfa47b0e6d3643efd8af2994b9
>
>
> -- 
> 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/cde6d369-8813-41ed-a1ea-253901014b46n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3829 bytes --]

  parent reply	other threads:[~2022-06-02  8:10 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 [this message]
     [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

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=cde6d369-8813-41ed-a1ea-253901014b46n@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).