From: Sylvain Hubert <champignoom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to wrap code blocks within new tables?
Date: Sat, 1 Jul 2023 00:58:33 -0700 (PDT) [thread overview]
Message-ID: <dcf7041b-c805-420b-ac60-07e6692e1577n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 922 bytes --]
Hi all,
I'm trying to create bounding boxes for code blocks by wrapping them inside
tables.
According to the manual, I should probably use some filter like:
function CodeBlock(elem)
return pandoc.Table(--[[... elem ...]])
end
but pandoc.Table takes a giant syntax tree with levels of all sorts of
nodes.
Neither the manual nor the error message gives a useful guide of actually
creating a table.
Could anyone provide a minimal example of creating a pandoc.Table in a lua
filter?
Thanks
--
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/dcf7041b-c805-420b-ac60-07e6692e1577n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1381 bytes --]
next reply other threads:[~2023-07-01 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 7:58 Sylvain Hubert [this message]
[not found] ` <dcf7041b-c805-420b-ac60-07e6692e1577n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-01 8:09 ` Sylvain Hubert
[not found] ` <4f0c1e08-60a7-4c97-9a7e-c3367ae32483n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-01 8:48 ` mf
[not found] ` <326e3767-e3b2-2bd3-5d60-340b2f1295bb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-01 9:01 ` Sylvain Hubert
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=dcf7041b-c805-420b-ac60-07e6692e1577n@googlegroups.com \
--to=champignoom-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).