From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc-rst: get rid of warnings at kernel-documentation.rst
Date: Wed, 20 Jul 2016 11:41:11 -0300 [thread overview]
Message-ID: <20160720114111.55d66e07@recife.lan> (raw)
In-Reply-To: <20160720083149.1ea84b43@lwn.net>
Em Wed, 20 Jul 2016 08:31:49 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Wed, 20 Jul 2016 16:23:28 +0200
> Markus Heiser <markus.heiser@darmarit.de> wrote:
>
> > Am 20.07.2016 um 16:11 schrieb Mauro Carvalho Chehab <mchehab@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
next prev parent reply other threads:[~2016-07-20 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 14:11 [PATCH] doc-rst: get rid of warnings at kernel-documentation.rst Mauro Carvalho Chehab
2016-07-20 14:23 ` Markus Heiser
2016-07-20 14:31 ` Jonathan Corbet
2016-07-20 14:41 ` Mauro Carvalho Chehab [this message]
2016-07-20 23:06 ` Jonathan Corbet
2016-07-21 10:22 ` Mauro Carvalho Chehab
2016-07-20 14:49 ` Markus Heiser
2016-07-20 15:06 ` Mauro Carvalho Chehab
2016-07-20 15:33 ` Markus Heiser
2016-07-21 10:25 ` Mauro Carvalho Chehab
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=20160720114111.55d66e07@recife.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.