From: Jonathan Corbet <corbet@lwn.net>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] doc: monospace style for inline code in botching ioctl
Date: Wed, 11 Jan 2023 15:59:57 -0700 [thread overview]
Message-ID: <874jswwuc2.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230102183649.9626-1-federico.vaga@vaga.pv.it>
Federico Vaga <federico.vaga@vaga.pv.it> writes:
> Highlighting inline code improves text readability.
>
> Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
It improves *HTML* text readability; the results for plain text are
... less clear. I think it's better to avoid this kind of extra markup
when we can.
Thanks,
jon
next prev parent reply other threads:[~2023-01-11 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 18:36 [PATCH V2] doc: monospace style for inline code in botching ioctl Federico Vaga
2023-01-11 22:59 ` Jonathan Corbet [this message]
2023-01-12 19:55 ` Federico Vaga
2023-01-12 20:33 ` Jonathan Corbet
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=874jswwuc2.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).