From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Fam Zheng <fam@euphon.net>, Qemu-block <qemu-block@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Aarushi Mehta <mehta.aaru20@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] sphinx: add qmp_lexer
Date: Wed, 22 May 2019 15:01:50 -0400 [thread overview]
Message-ID: <4005ff30-2df3-c615-7fed-fd9d5de56e95@redhat.com> (raw)
In-Reply-To: <CAFEAcA9mEHvQ9TBGpvfVoDx-pKB9Cyc-JWeUUh2Hc0Uxb1GjuQ@mail.gmail.com>
On 5/22/19 4:49 AM, Peter Maydell wrote:
> On Tue, 21 May 2019 at 21:07, John Snow <jsnow@redhat.com> wrote:
>>
>> 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 notations.
>
>> diff --git a/docs/sphinx/qmp_lexer.py b/docs/sphinx/qmp_lexer.py
>> new file mode 100644
>> index 0000000000..f619f11139
>> --- /dev/null
>> +++ b/docs/sphinx/qmp_lexer.py
>> @@ -0,0 +1,34 @@
>> +# QEMU Monitor Protocol Lexer Extension
>> +#
>> +# Copyright (C) 2019, Red Hat Inc.
>> +#
>> +# Authors:
>> +# Eduardo Habkost <ehabkost@redhat.com>
>> +# John Snow <jsnow@redhat.com>
>> +#
>> +# This work is licensed under the terms of the GNU GPL, version 2. See
>> +# the COPYING file in the top-level directory.
>
> Did you definitely mean 2-only and not 2-or-later ?
>
> thanks
> -- PMM
>
Copy-paste pulled from another Python script. 2 or later is fine by me;
I can resend if desired (or, I'd be fine with anyone touching it up in
post.)
next prev parent reply other threads:[~2019-05-22 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:06 [Qemu-devel] [PATCH 0/2] Add QMP lexer for annotated JSON to Sphinx John Snow
2019-05-21 20:06 ` [Qemu-devel] [PATCH 1/2] sphinx: add qmp_lexer John Snow
2019-05-21 20:28 ` Eduardo Habkost
2019-05-22 8:49 ` Peter Maydell
2019-05-22 17:51 ` Eduardo Habkost
2019-05-22 19:01 ` John Snow [this message]
2019-05-22 21:11 ` Peter Maydell
2019-05-21 20:06 ` [Qemu-devel] [PATCH 2/2] docs/bitmaps: use QMP lexer instead of json John Snow
2019-05-21 20:28 ` Eduardo Habkost
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=4005ff30-2df3-c615-7fed-fd9d5de56e95@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).