From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: AW: What might be a good way to process macro's in markdown
Date: Sun, 12 Dec 2021 17:56:34 +0000 [thread overview]
Message-ID: <47a030fe791048779b1ee789f0e3749c@unibe.ch> (raw)
In-Reply-To: <ea6c613e-6f98-4db4-b714-3b2fce85c090n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Have a look at http://christophe.delord.free.fr/pp/
________________________________________
Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> im Auftrag von Pum Walters <pum.walters-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Gesendet: Sonntag, 12. Dezember 2021 15:46:45
An: pandoc-discuss
Betreff: What might be a good way to process macro's in markdown
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@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<https://groups.google.com/d/msgid/pandoc-discuss/ea6c613e-6f98-4db4-b714-3b2fce85c090n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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/47a030fe791048779b1ee789f0e3749c%40unibe.ch.
next prev parent reply other threads:[~2021-12-12 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 14:46 Pum Walters
[not found] ` <ea6c613e-6f98-4db4-b714-3b2fce85c090n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-12 17:56 ` denis.maier-NSENcxR/0n0 [this message]
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=47a030fe791048779b1ee789f0e3749c@unibe.ch \
--to=denis.maier-nsencxr/0n0@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).