From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Transform a fenced div to mkdocs markdown admonition format
Date: Sat, 05 Nov 2022 09:03:20 +0100 [thread overview]
Message-ID: <87a6556cg2.fsf@zeitkraut.de> (raw)
In-Reply-To: <CAM4RMshtHUuFSHryQqAgquMduCd5xSM7c2CKnvR0H1=zsg2xQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Aidan Reilly <aireilly-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
> Trying this, but it's just passing the text of the admonition block
> through
The order of spaces and newline in the replacement was switched. After
some playing around, this is the filter I came up with:
``` lua
local admonitions = {
warning = '!!! warning',
note = '!!! note',
tip = '!!! tip',
important = '!!! important',
caution = '!!! caution'
}
local opts = PANDOC_WRITER_OPTIONS -- reuse options to render snippets
opts.columns = opts.columns - 4 -- admons are indented by four spaces
opts.template = nil -- render a snippet
function Div (div)
local admonition_text = admonitions[div.classes[1]]
if not admonition_text then return nil end -- not an admonition: bail
local md = admonition_text .. '\n' ..
pandoc.write(pandoc.Pandoc(div.content), 'markdown', opts)
return pandoc.RawBlock(
'markdown',
md:gsub('\n*$', '') -- remove trailing newlines
:gsub('\n', '\n ') -- indent block
)
end
```
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-11-05 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 16:14 Aidan Reilly
[not found] ` <ddc82450-b82b-4b8f-9d5f-30c6a28c206fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-03 20:09 ` John MacFarlane
[not found] ` <7AF275BD-12EB-4424-84E5-1A45FF675520-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-03 20:40 ` Aidan Reilly
[not found] ` <CAM4RMsh1iqDjA7WqfCuWJV4NCD_ELXfFL0iV+pGUWASvgAzq5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-03 20:55 ` Aidan Reilly
[not found] ` <CAM4RMsj6rwDLDmNxNzvUDODw0qa5NZgZtbAS_ozf+XJ3ZE+jHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-03 21:00 ` Albert Krewinkel
[not found] ` <87h6zf698z.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-04 0:25 ` Aidan Reilly
[not found] ` <CAM4RMshtHUuFSHryQqAgquMduCd5xSM7c2CKnvR0H1=zsg2xQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-05 8:03 ` Albert Krewinkel [this message]
[not found] ` <87a6556cg2.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-05 13:09 ` Aidan Reilly
[not found] ` <CAM4RMsiRRywBgcHHQgfUxV5BZQfQw5sgqy44za4VC9=_TmqYPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-05 13:10 ` Aidan Reilly
2022-11-05 13:53 ` Albert Krewinkel
[not found] ` <875yft5wqc.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-05 16:26 ` Aidan Reilly
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=87a6556cg2.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).