public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Pum Walters <pum.walters-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: What might be a good way to process macro's in markdown
Date: Sun, 12 Dec 2021 06:46:45 -0800 (PST)	[thread overview]
Message-ID: <ea6c613e-6f98-4db4-b714-3b2fce85c090n@googlegroups.com> (raw)


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

What might be a good way to use and process macro's in Markdown. The docs 
have an example of variable-substitution, but not of more general macro's.

A macro might look something like     
*  ... ordinary markdown ...*

*  <<* name args >> *

*    ...body... *
*  <</ name >>*

*  ... ordinary markdown ...*

where:

   - the name is an identifier
   - each arg is an identifier, number or string in quotes
   - the body is arbitrary text
   - Obviously, the parentheses <<*, <</ and >> could be anything that the 
   parser could recognise
   
Ideally, processing can be done in Lua, and the result of the macro is to 
be processed further, to generate Markdown, LaTeX, HTML or other languages.

Any thoughts?

-- 
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/ea6c613e-6f98-4db4-b714-3b2fce85c090n%40googlegroups.com.

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

             reply	other threads:[~2021-12-12 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 14:46 Pum Walters [this message]
     [not found] ` <ea6c613e-6f98-4db4-b714-3b2fce85c090n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-12 17:56   ` AW: " denis.maier-NSENcxR/0n0
2021-12-12 18:12   ` John MacFarlane

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=ea6c613e-6f98-4db4-b714-3b2fce85c090n@googlegroups.com \
    --to=pum.walters-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).