From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jani Nikula <jani.nikula@intel.com>,
Markus Heiser <markus.heiser@darmarit.de>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] Revert "Revert "doc/sphinx: Enable keep_warnings""
Date: Tue, 9 Aug 2016 08:07:48 -0600 [thread overview]
Message-ID: <20160809080748.18fef9d4@lwn.net> (raw)
In-Reply-To: <CAKMK7uFrhbC+juwCsj_kHUdj0_F1XZFQ8b1_OQt_cNF5+vBpdA@mail.gmail.com>
On Tue, 9 Aug 2016 15:56:15 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > So I honestly think we should just set the highlight language to "none" by
> > default. The syntax highlighting in code samples adds some colorful sugar
> > to the docs, but it's not really all that useful, IMO, and people who want
> > it can override the language in the right places.
> >
> > Any strong opposition to this idea?
>
> Hm right, didn't realize that this is where it's coming from. No
> strong opinion from my side on highlighting the C block quotes really.
> Otoh that highlighting is rather pretty. Could we perhaps just shut
> sphinx up about the "C" highlighting issues?
We can look into that, but, in the end, we'll always have a lot of literal
blocks that are not C code. Even if Sphinx doesn't warn about them, it
tries to mark them up as C with occasionally strange results. I'm not
really convinced it's a net win.
jon
next prev parent reply other threads:[~2016-08-09 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 16:23 [PATCH] Revert "Revert "doc/sphinx: Enable keep_warnings"" Daniel Vetter
2016-08-08 21:32 ` Jonathan Corbet
2016-08-09 13:56 ` Daniel Vetter
2016-08-09 14:07 ` Jonathan Corbet [this message]
2016-08-09 14:11 ` Markus Heiser
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=20160809080748.18fef9d4@lwn.net \
--to=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
/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).