From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: Fam Zheng <fam@euphon.net>,
Peter Maydell <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>,
Aarushi Mehta <mehta.aaru20@gmail.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/3] Add QMP lexer for annotated JSON to Sphinx
Date: Mon, 3 Jun 2019 17:46:50 -0400 [thread overview]
Message-ID: <20190603214653.29369-1-jsnow@redhat.com> (raw)
QMP isn't json. It turns out Pygments cares about this.
Teach Pygments to go with the annotated flow.
V3:
- Also annotate elision indicators '...', which cause
problems in Sphinx 2.1+
- Adjust setup.py to cope with future versions of Sphinx
that change the add_lexer interface
V2:
- Change GPL2 to GPLv2+ (Peter Maydell)
- Change "highlights" to "lexes" in docstrings
- Fix typo ("Sphinx()" => "Sphinx") in docstring
Reported-by: Aarushi Mehta <mehta.aaru20@gmail.com>
John Snow (3):
docs/interop/bitmaps.rst: Fix typos
sphinx: add qmp_lexer
docs/bitmaps: use QMP lexer instead of json
docs/conf.py | 4 +--
docs/interop/bitmaps.rst | 58 ++++++++++++++++++++--------------------
docs/sphinx/qmp_lexer.py | 43 +++++++++++++++++++++++++++++
3 files changed, 74 insertions(+), 31 deletions(-)
create mode 100644 docs/sphinx/qmp_lexer.py
--
2.20.1
next reply other threads:[~2019-06-03 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 21:46 John Snow [this message]
2019-06-03 21:46 ` [Qemu-devel] [PATCH v3 1/3] docs/interop/bitmaps.rst: Fix typos John Snow
2019-06-05 14:28 ` Vladimir Sementsov-Ogievskiy
2019-06-03 21:46 ` [Qemu-devel] [PATCH v3 2/3] sphinx: add qmp_lexer John Snow
2019-06-07 10:27 ` Peter Maydell
2019-06-03 21:46 ` [Qemu-devel] [PATCH v3 3/3] docs/bitmaps: use QMP lexer instead of json John Snow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190603214653.29369-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=mehta.aaru20@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).