Em Wed, 20 Jul 2016 08:31:49 -0600 Jonathan Corbet <cor...@lwn.net> escreveu:
> On Wed, 20 Jul 2016 16:23:28 +0200 > Markus Heiser <markus.hei...@darmarit.de> wrote: > > > Am 20.07.2016 um 16:11 schrieb Mauro Carvalho Chehab > > <mche...@s-opensource.com>: > > > > > Sphinx 1.4.5 complains about some literal blocks at > > > kernel-documentation.rst: > > > > > > Documentation/kernel-documentation.rst:373: WARNING: Could not lex > > > literal_block as "C". Highlighting skipped. > > > Documentation/kernel-documentation.rst:378: WARNING: Could not lex > > > literal_block as "C". Highlighting skipped. > > > Documentation/kernel-documentation.rst:576: WARNING: Could not lex > > > literal_block as "C". Highlighting skipped. > > > > > > Fix it by telling Sphinx to consider them as "none" type. > > > > Hi Mauro, > > > > IMHO we should better fix this by unsetting the lexers default language > > in the conf.py [1] ... currently: > > > > highlight_language = 'C' # set this to 'none' > > > > As far as I know the default highlight_language is also the default > > for literal blocks starting with "::" > > The thing with that is that a lot of literal blocks *do* have C code, even > in kernel-documentation.rst. Setting that in conf.py would turn off all C > highlighting. I think that might actually be a desirable outcome, but it > would be good to make that decision explicitly. Agreed. Assuming "C" as default seems a good idea to me. > > As it happens, I'd already fixed these particular warnings in docs-next: > > http://permalink.gmane.org/gmane.linux.documentation/39806 > > I took a different approach; using code-block might actually be better. Particularly, I prefer to explicitly tell when a block has a different highlight than to switch the default along the document with "highlight" tag, as this can be trickier to maintain as the document suffers review along the time. Anyway, your call ;) Thanks, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
