From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Craig Parker <craigp-UzRat0APdLvLPIzirxu/xA@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Conditional Formatting
Date: Tue, 17 Sep 2019 16:38:50 -0700 [thread overview]
Message-ID: <yh480kr24eh4s5.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <214b77f6-5739-eba4-ff5d-ea5d1fa553b9-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
Craig Parker <craigp-UzRat0APdLvLPIzirxu/xA@public.gmane.org> writes:
> So if I define a ul.shallow and a ul.deep in my css, you're saying a lua
> filter would render (in the html) <ul class="shallow"> and <ul
> class="deep"> ?
No, I'm not saying that.
You could write a lua filter that would identify "shallow" and
"deep" lists, and insert a div with class "shallow" or "deep"
around the list.
Css could then have a rule like .shallow > ul or .deep > ul.
> Are creating lua filters anything like coding in other languages? I know
> bash and PHP...
sort of, yes. See the documentation for lua filters on the pandoc
website.
next prev parent reply other threads:[~2019-09-17 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 18:51 Craig Parker
[not found] ` <34b81ee8-2405-5b3a-bbc9-23600a2802c5-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
2019-09-17 19:11 ` John MacFarlane
[not found] ` <yh480ktv9ahh68.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-17 19:21 ` Craig Parker
[not found] ` <214b77f6-5739-eba4-ff5d-ea5d1fa553b9-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
2019-09-17 23:38 ` John MacFarlane [this message]
[not found] ` <yh480kr24eh4s5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-18 14:12 ` BP Jonsson
[not found] ` <CAFC_yuQ3GEoYovUB+tg6iSs_hL9bDGq7RCoDT93GemZXz+CSYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-18 14:46 ` Craig Parker
[not found] ` <99b9af3a-c206-d664-3b58-d671eabd9116-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
2019-09-18 15:32 ` John Gabriele
2019-09-19 5:15 ` brainchild
[not found] ` <c18b9c78-2262-4f63-b995-0698dc795132-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-19 11:14 ` Craig Parker
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=yh480kr24eh4s5.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=craigp-UzRat0APdLvLPIzirxu/xA@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).