diff options
| author | John Snow | 2019-07-10 21:08:06 +0200 |
|---|---|---|
| committer | John Snow | 2019-07-10 21:08:06 +0200 |
| commit | cd231e13bdcb8d686b014bef940c7d19c6f1e769 (patch) | |
| tree | 80d259ae02f5cc7eb000a3623fc0e53dced536aa /docs/interop/bitmaps.rst | |
| parent | docs/interop/bitmaps.rst: Fix typos (diff) | |
| download | qemu-cd231e13bdcb8d686b014bef940c7d19c6f1e769.tar.gz qemu-cd231e13bdcb8d686b014bef940c7d19c6f1e769.tar.xz qemu-cd231e13bdcb8d686b014bef940c7d19c6f1e769.zip | |
sphinx: add qmp_lexer
Sphinx, through Pygments, does not like annotated json examples very
much. In some versions of Sphinx (1.7), it will render the non-json
portions of code blocks in red, but in newer versions (2.0) it will
throw an exception and not highlight the block at all. Though we can
suppress this warning, it doesn't bring back highlighting on non-strict
json blocks.
We can alleviate this by creating a custom lexer for QMP examples that
allows us to properly highlight these examples in a robust way, keeping
our directionality and elision notations.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
Reported-by: Aarushi Mehta <mehta.aaru20@gmail.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Message-id: 20190603214653.29369-3-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
Diffstat (limited to 'docs/interop/bitmaps.rst')
0 files changed, 0 insertions, 0 deletions