Re: How to manipuate <code> block instead of <pre>

["blind.line" <blind.line.drawing-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

Sweet that looks perfect. 

Thanks,

James

> On Sep 12, 2020, at 01:35, Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> wrote:
> 
> 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
> 
> -- 
> You received this message because you are subscribed to a topic in the Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/pandoc-discuss/DlJW1NE48W0/unsubscribe.
> To unsubscribe from this group and all its topics, 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/87een7l89k.fsf%40zeitkraut.de.

-- 
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/E0A96D8F-922D-4866-9023-891BF0B16F10%40gmail.com.