public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
To: Pandoc Mailing List
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Complete sample writer using 3.0 syntax
Date: Tue, 23 May 2023 20:22:19 -0400	[thread overview]
Message-ID: <036dd5f8-667a-2b2f-9eaa-76c29718cd55@meddatainc.com> (raw)

As a newcomer to pandoc I could greatly benefit from a /complete/ sample custom writer using the 3.0 syntax as I am muddling my way through learning it.

Googling finds a lot of code fragments using the old AST syntax which is now deprecated. The github repository referenced on the pandoc website has a lot of old syntax code but no code using the new syntax. Further, the github page has a warning that the site should no longer be used.

Where can I find a complete lua writer using the new syntax? Does not need to be a sophisticated writer, perhaps just making some customization of HTML output as such just to get the feet wet.

-- 
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/036dd5f8-667a-2b2f-9eaa-76c29718cd55%40meddatainc.com.


             reply	other threads:[~2023-05-24  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  0:22 H [this message]
     [not found] ` <036dd5f8-667a-2b2f-9eaa-76c29718cd55-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-24  1:01   ` John MacFarlane
     [not found]     ` <EB4E4875-E1E0-48F7-9379-20FEF966E944-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-24 16:31       ` H

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=036dd5f8-667a-2b2f-9eaa-76c29718cd55@meddatainc.com \
    --to=agents-fczobrvlydubuy7/sjonfg@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).