Posted by oddhack on May 24, 2020; 2:13pm
URL: https://discuss.asciidoctor.org/Passing-options-to-configuring-source-highlighters-tp8047.html

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?