All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Joe Perches <joe@perches.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: Update the preferred line size to 100 characters
Date: Thu, 20 Jan 2022 11:55:46 +0200	[thread overview]
Message-ID: <YekxouspRBkzHpKO@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20220119160642.140e84c6@gandalf.local.home>

Hi Steven,

Thank you for cc'ing me.

On Wed, Jan 19, 2022 at 04:06:42PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> 
> As commit bdc48fa11e46f ("checkpatch/coding-style: deprecate 80-column
> warning") states:
> 
>     Increase the default limit to 100 characters.  Not because 100
>     characters is some hard limit either, but that's certainly a "what are
>     you doing" kind of value and less likely to be about the occasional
>     slightly longer lines.
> 
> It's 2022, people are not using 80x24 terminals anymore (well I'm sure
> someone is, but they are the small minority).
> 
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
>  Documentation/process/coding-style.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
> index 03eb53fd029a..73be9edffede 100644
> --- a/Documentation/process/coding-style.rst
> +++ b/Documentation/process/coding-style.rst
> @@ -101,10 +101,10 @@ Get a decent editor and don't leave whitespace at the end of lines.
>  Coding style is all about readability and maintainability using commonly
>  available tools.
>  
> -The preferred limit on the length of a single line is 80 columns.
> +The preferred limit on the length of a single line is 100 columns.
>  
> -Statements longer than 80 columns should be broken into sensible chunks,
> -unless exceeding 80 columns significantly increases readability and does
> +Statements longer than 100 columns should be broken into sensible chunks,
> +unless exceeding 100 columns significantly increases readability and does
>  not hide information.

As others have already opined, I agree that increasing the line length from
80 isn't going to make the code universally (or even mostly) more readable.
There are probably cases it does but this is not necessarily common.

I think the original text puts it well: there is a limit of 80 but that is
not a hard limit. When reviewing code, I often ask to wrap lines if there's
really no reason to keep them longer (in this case that seldom is the only
problem with the code). Of course you could argue what these reasons might
be. At the very least indentation has a higher precedence that the line
length. This is also written in the documentation.

My view is that this recommendation is not, at least today, relevant for
the purpose of making the code readable for someone with a VT100 terminal,
but a part of a recipe for writing good code simply expressed in units
everyone knows: VT100 terminal size. Also 80x24 is still the default window
size of many if not most terminal emulators.

-- 
Kind regards,

Sakari Ailus

      parent reply	other threads:[~2022-01-20  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 21:06 [PATCH] docs: Update the preferred line size to 100 characters Steven Rostedt
2022-01-19 23:00 ` Randy Dunlap
2022-01-20  0:36   ` Joe Perches
2022-01-20  9:55 ` Sakari Ailus [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=YekxouspRBkzHpKO@paasikivi.fi.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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.