public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Converting filter to custom writer
Date: Wed, 29 Jun 2022 18:23:00 +0200	[thread overview]
Message-ID: <CADAJKhBPpu1=FnxP0byMDWGEBF-7XAV7mVc+TzDSPX2t2GXN=g@mail.gmail.com> (raw)
In-Reply-To: <CADAJKhAyQY_deNGV4SN61jodEM4sLUBSa4zpdxRdXg8+LLMzTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]

I saw no answer to this one. Hopefully it just got lost.
Apologies to anyone who already got it.

Den fre 24 juni 2022 16:09BPJ <> skrev:

> I have a not-so-old "pseudo-writer" implemented as a filter which mostly
> injects  tons of raw markup into the document tree so that the output of
> the plain writer looks like my target format, returning a table of filters
> at the end like this
>
> ``````lua
> return {
>   {
>     Meta = get_config
>   },
>   {
>     SmallCaps = SmallCaps,
>     Str = Str
>   },
>   note_filter,
>   main_filter
> }
> ``````
>
> where `get_config` just extracts some info from the metadata and populates
> a table declared at the top of the script which the functions in the other
> filters refer to.
>
> Am I right that I in principle could convert this into a new style custom
> writer by removing the Meta filter, replacing `return {<filters>}` above
> with `local filters = {<filters>}` and adding the following at the bottom
> of the script?
>
> ``````lua
> function Writer (doc, opts)
>   get_config(doc.meta)
>   for _,filter in ipairs(filters) do
>     doc = doc:walk(filter)
>   end
>   doc.blocks = blocks
>   return pandoc.write(doc, 'plain', opts)
> ``````
>
> (This got me thinking: what if `walk` accepted one more argument which
> will be passed as an extra argument to the functions in the filters, which
> could be used to pass config and/or maintain state? It somehow feels more
> intuitive than defining a table outside the metadata handler which all
> handlers close around.)
>
> (BTW the main reason that the `note_filter` is separate is that it needs
> to be topdown because it counts and collects the notes, while `main_filter`
> needs to be bottomup because it sometimes relies on the content of elements
> already having been processed. I was very happy when I realized that this
> would work!)
>
>

-- 
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/CADAJKhBPpu1%3DFnxP0byMDWGEBF-7XAV7mVc%2BTzDSPX2t2GXN%3Dg%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 3573 bytes --]

  parent reply	other threads:[~2022-06-29 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 14:09 BPJ
     [not found] ` <CADAJKhAyQY_deNGV4SN61jodEM4sLUBSa4zpdxRdXg8+LLMzTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-29 16:23   ` BPJ [this message]
2022-06-29 17:22     ` Albert Krewinkel

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='CADAJKhBPpu1=FnxP0byMDWGEBF-7XAV7mVc+TzDSPX2t2GXN=g@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).