#31 adding pygments options to code directive

[Anonymous]

some pygments lexers support options (notably the pycon lexer supports a python3 flag that enables python3 support).
the attached patch propose to support passing options to pygments using this syntax:

.. code:: pycon
:pygments-options: python3

>>> print("coucou")
coucou

remark:
the attached patch supports a list of key[=value] as pygments-options content, but values can not be lists, which would be needed to support all pygments lexer options.

[Anonymous]

prototype implementation

[Günter Milde]

How about separating the pygments-options by newlines in the input to
allow list arguments?

.. code:: lua
   :pygments-options: disabled_modules = foo, bar
                      ensurenl = True

[Dmitry Shachnev]

I have now attached an updated patch version in patches/112.

[Ben Ramsey]

Is this something the project is still considering? I'd love to have the ability to pass additional Pygments options. How can I help make this happen?

[Günter Milde]

Is this something the project is still considering?
It is not ruled out but also not a high priority todo item.

I'd love to have the ability to pass additional Pygments options. How can I help make this happen?
A generic starter for contributors is in the Docutils documentation under
http://docutils.sourceforge.net/docs/dev/policies.html#how-to-get-a-new-feature-into-docutils.

For ideas in this particular case, have a look at the suggestions and preconditions in the discussion of patch/112.

For help on getting started and discussion of details, the docutils-devel mail list may be a good place.

[Günter Milde]

Closing as duplicate: Discussion moved to
patches/112.