On Apr 10, 12:52 am, Max Battcher <[email protected]> wrote: > Also, if your input/output formats follow an expected, parse-able > format, you may want to consider writing a Pygments (pygments.org) lexer > for the format, if one doesn't already exist. Writing a lexer is > actually reasonably easy and there are plenty of examples to draw from > in Pygments' source code. That can give you nice syntax highlighting of > your input/output formats using the .. code-block:: yourlanguage directive.
I took your advice and it was straight-forward as you said; results are great. The ``.. highlight`` directive even makes it easy to define a language default on an entire document. Thanks! \malthe -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
