Passing options to / configuring source highlighters

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Passing options to / configuring source highlighters

oddhack
I'm migrating a LaTeX document that makes extensive use of the listings package with hundreds of custom keywords in their C++ code, and lots of use of \lstinline to get highlighting of code in body text. I see @mojavelinux is doing some experimenting with inline code formatting, so maybe that will be available in time. But more broadly, how can I configure the underlying highlighters beyond the handful of attributes I can set in asciidoctor markup OOTB? Pygments, for example, has its own extensive set of options and plugin API for custom formatters, which provides a way to support the custom keywords this document uses - but how do I get at that configurability through the asciidoctor interface?
Reply | Threaded
Open this post in threaded view
|

Re: Passing options to / configuring source highlighters

oddhack
Ah, I see there is some advice on pygments in 46.5.3 of the user manual. Missed that initially. The inline issue is still quite relevant to us, though, so I hope that remains active.