From: "Marcus Rohrmoser" <me+pandoc-cOhbpZe5kZ8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Front Matter from md to html
Date: Wed, 25 May 2022 12:05:25 +0200 [thread overview]
Message-ID: <8296520A-9592-4A68-9889-6B1F231DF452@mro.name> (raw)
In-Reply-To: <Yo3e1RpzbXF6u3cp@localhost>
On 25 May 2022, at 9:46, Bastien DUMONT wrote:
> Is there a reason you don't use the YAML header for that?
It didn't occur to me to patch the template! Uh.
This looks perfectly doable, thanks and solves 75% of my use case.
For more post-processing (updating tag index pages etc.) I can inspect
the html result.
Thanks!
prev parent reply other threads:[~2022-05-25 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 7:13 Marcus Rohrmoser
[not found] ` <78E2A0F6-02FD-43AD-8F09-03B3441CBFF8-cOhbpZe5kZ8@public.gmane.org>
2022-05-25 7:46 ` Bastien DUMONT
2022-05-25 10:05 ` Marcus Rohrmoser [this message]
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=8296520A-9592-4A68-9889-6B1F231DF452@mro.name \
--to=me+pandoc-cohbpze5kz8@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).