From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to manipuate <code> block instead of <pre>
Date: Sat, 12 Sep 2020 10:16:39 +0200 [thread overview]
Message-ID: <87een7l89k.fsf@zeitkraut.de> (raw)
In-Reply-To: <cac0e082-2af2-420b-ad6d-aef9afc1c2f9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Please checkout
<https://github.com/pandoc/lua-filters/tree/master/revealjs-codeblock>,
it should help with your issue.
J. E. Marca writes:
> Hi all,
>
> (Apologies in advance if the online editor mangles this post, as I'm
> writing lots html pre tags)
>
> I use pandoc to generate reveal.js presentations. All works well if I let
> pandoc do its thing.
>
>
> However, was looking through the reveal.js v4 docs, and there is a really
> useful hack to highlight successive lines of a code block. See
> https://revealjs.com/code/#step-by-step-highlights.
>
> To use it, the reveal.js docs say to add "data-line-numbers" inside of the
> <code> tag. For example:
>
> ```
> <pre><code data-line-numbers="3-5|8-10|13-15">
> ...
>
> ```
>
>
> That is difficult in pandoc at the moment, as access to the <code> block
> attributes is prevented (see also pandoc issue
> [#3858](https://github.com/jgm/pandoc/issues/3858))
>
>
> Using this:
>
> ```{.bash data-line-numbers="1,2,3,4|4|2|3"}
> osmium extract \
> -p port-au-prince-poly.osm \
> -o port-au-prince-latest.osm \
> haiti-and-domrep-latest.osm.pbf
> ```
>
> produces:
>
> <pre class="bash" data-line-numbers="1,2,3,4|4|2|3" ><code ...
>
>
> I want the data-line-numbers and in fact the class=bash (or
> class=language-bash" ) to be on the code block.
>
>
> The issue I referenced above (#3858) was opened in August 2017 so I'm not
> hopeful for any movement from pandoc. But, it would be useful if there was
> yet another command line switch to force all code markup to occur on the
> <code> block, OR the <pre> block, OR both. Esp. given that the HTML
> recommendation still suggests putting language-*** class inside the <code>
> block.
>
>
> Any other ways around this? My current solution is just to straight up use
> <pre><code foo=bar etc=etc> tags inside my markdown, which I hate doing as
> it means I'm only targeting reveal.js.
>
>
> Thanks,
> James Marca
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2020-09-12 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 21:05 J. E. Marca
[not found] ` <cac0e082-2af2-420b-ad6d-aef9afc1c2f9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-12 8:16 ` Albert Krewinkel [this message]
[not found] ` <87een7l89k.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-12 18:50 ` blind.line
2020-09-12 20:22 ` blind.line
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=87een7l89k.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).