[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <7BE8882B-2302-4B88-848D-308159361A1F@darmarit.de>
Date: Tue, 9 Aug 2016 16:11:19 +0200
From: Markus Heiser <markus.heiser@...marit.de>
To: Jonathan Corbet <corbet@....net>
Cc: Daniel Vetter <daniel.vetter@...ll.ch>,
LKML <linux-kernel@...r.kernel.org>,
Jani Nikula <jani.nikula@...el.com>,
Daniel Vetter <daniel.vetter@...el.com>
Subject: Re: [PATCH] Revert "Revert "doc/sphinx: Enable keep_warnings""
Am 09.08.2016 um 16:07 schrieb Jonathan Corbet <corbet@....net>:
> On Tue, 9 Aug 2016 15:56:15 +0200
> Daniel Vetter <daniel.vetter@...ll.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
Hi, as far as I know, there is no option to suppress warnings
from the lexer [1]. What's about "highlight_language = 'guess'" ...
I compiled gpu and the warnings disappear, but I have not yet
looked at the complete results in HTML.
[1] FYI: Sphinx's lexer is http://pygments.org/
--M--
Powered by blists - more mailing lists