From: Jani Nikula <jani.nikula@linux.intel.com>
To: Markus Heiser <markus.heiser@darmarit.de>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jim Davis <jim.epost@gmail.com>,
linux-kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 0/4] Fix PDF build errors
Date: Thu, 03 Nov 2016 11:11:45 +0200 [thread overview]
Message-ID: <87vaw5hqr2.fsf@intel.com> (raw)
In-Reply-To: <1F43ABDB-381F-4AC8-8A72-AD0FCBE96DE0@darmarit.de>
On Wed, 02 Nov 2016, Markus Heiser <markus.heiser@darmarit.de> wrote:
> Am 02.11.2016 um 17:47 schrieb Mauro Carvalho Chehab <mchehab@infradead.org>:
>> I'm staring to think that we should just redefine the default for ::
>> to be "none", and use the "C" handling **only** when explicitly
>> requested.
>>
>> I remember that Jon did such suggestion sometime ago.
>
> *shrug* ... I think about kernel-doc comments in the sources,
> mostly you will have small examples and won't those verbose
> ".. code-block::" markup / using "::" keeps the comment compact.
I sent the patch [1] to default to "none". It's never wrong, not even
for code. But getting the highlighting wrong, OTOH, is pretty bad. We
have that.
And really, if you look at the kernel-doc comments and the rst
documentation, we don't have all that many literal blocks that would
benefit from syntax highlighting in the first place.
BR,
Jani.
[1] http://lkml.kernel.org/r/1478164053-4562-1-git-send-email-jani.nikula@intel.com
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2016-11-03 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 22:44 [PATCH RFC 0/4] Fix PDF build errors Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 1/4] docs-rst: fix " Mauro Carvalho Chehab
2016-11-02 15:03 ` Markus Heiser
2016-11-02 15:06 ` Markus Heiser
2016-11-01 22:44 ` [PATCH RFC 2/4] [media] subdev-formats.rst: we need a pdf picture for bayer Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 3/4] [media] subdev-formats.rst: don't use adjustbox on a longtable Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 4/4] [media] subdev-formats.rst: add missing columns to tabularcolumns Mauro Carvalho Chehab
2016-11-01 22:53 ` [PATCH RFC 0/4] Fix PDF build errors Mauro Carvalho Chehab
2016-11-02 11:14 ` Jani Nikula
2016-11-02 12:20 ` Mauro Carvalho Chehab
2016-11-02 13:27 ` Jani Nikula
2016-11-02 16:36 ` Mauro Carvalho Chehab
2016-11-02 21:47 ` Fengguang Wu
2016-11-02 16:08 ` Markus Heiser
2016-11-02 16:47 ` Mauro Carvalho Chehab
2016-11-02 17:07 ` Markus Heiser
2016-11-03 9:11 ` Jani Nikula [this message]
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=87vaw5hqr2.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=mchehab@osg.samsung.com \
/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).