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: Mon, 8 Aug 2016 15:32:35 -0600 [thread overview]
Message-ID: <20160808153235.188f6d1d@lwn.net> (raw)
In-Reply-To: <1470673391-13635-1-git-send-email-daniel.vetter@ffwll.ch>
On Mon, 8 Aug 2016 18:23:11 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Even with Markus fixes to the importer I still get warnigns from
> sphinx which are entirely bogus :(
>
> /home/daniel/linux/src/Documentation/gpu/drm-kms.rst:13: WARNING: Could not lex literal_block as "C". Highlighting skipped.
> /home/daniel/linux/src/Documentation/gpu/drm-kms-helpers.rst:16: WARNING: Could not lex literal_block as "C". Highlighting skipped.
> /home/daniel/linux/src/Documentation/gpu/i915.rst:57: WARNING: Could not lex literal_block as "C". Highlighting skipped.
>
> Well it's worse: Those are warnings which don't even show up with this
> enabled. Just sending this out again in the hopes some has a clue
> what's going on.
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?
jon
next prev parent reply other threads:[~2016-08-08 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 16:23 Daniel Vetter
2016-08-08 21:32 ` Jonathan Corbet [this message]
2016-08-09 13:56 ` Daniel Vetter
2016-08-09 14:07 ` Jonathan Corbet
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=20160808153235.188f6d1d@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
all inboxes | Powered by JetHome®