From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"qemu devel list" <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH RESEND] manual: escape backslashes in "parsed-literal" blocks
Date: Wed, 9 Sep 2020 13:09:25 +0200 [thread overview]
Message-ID: <f4289f81-1927-33a3-333b-eee552f02632@redhat.com> (raw)
In-Reply-To: <3c2d2a59-b556-180d-5a74-5fe74d46ccd2@redhat.com>
On 09/08/20 20:14, Philippe Mathieu-Daudé wrote:
> On 9/8/20 7:21 PM, Laszlo Ersek wrote:
>> According to
>> <https://docutils.sourceforge.io/docs/ref/rst/directives.html#parsed-literal>,
>> "inline markup is recognized and there is no protection from parsing.
>> Backslash-escapes may be necessary to prevent unintended parsing".
>>
>> The qemu(1) manual page (formatted with Sphinx 2.2.2) has several overlong
>> lines on my system. A stand-alone backslash at EOL serves as line
>> continuation in a "parsed-literal" block. Therefore, escape the
>> backslashes that we want to appear as such in the formatted documentation.
>>
>> Cc: Peter Maydell <peter.maydell@linaro.org>
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> ---
>>
>> Notes:
>> Resending with Peter's email address in the Cc: tag fixed. Sorry!
>>
>> docs/system/device-url-syntax.rst.inc | 8 +-
>> qemu-options.hx | 108 ++++++++++----------
>> 2 files changed, 58 insertions(+), 58 deletions(-)
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
Thanks for the quick check!
Laszlo
next prev parent reply other threads:[~2020-09-09 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 17:21 [PATCH RESEND] manual: escape backslashes in "parsed-literal" blocks Laszlo Ersek
2020-09-08 18:14 ` Philippe Mathieu-Daudé
2020-09-09 11:09 ` Laszlo Ersek [this message]
2020-09-10 10:23 ` Philippe Mathieu-Daudé
2020-09-15 7:57 ` Laszlo Ersek
2020-09-16 8:53 ` Laurent Vivier
2020-09-16 13:31 ` Laszlo Ersek
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=f4289f81-1927-33a3-333b-eee552f02632@redhat.com \
--to=lersek@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).