From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@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: Wed, 19 Jan 2022 16:36:42 -0800 [thread overview]
Message-ID: <7e6d37612af05c7c21fc7b06462ccf0da1b8d062.camel@perches.com> (raw)
In-Reply-To: <d7130556-a8a4-76c0-0fde-b6b1439efda6@infradead.org>
On Wed, 2022-01-19 at 15:00 -0800, Randy Dunlap wrote:
>
> On 1/19/22 13:06, 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.
>
>
> Has Linus has changed his view on this since 2016?
> https://lore.kernel.org/all/CA+55aFxaOFoh+Zrm5tNhU4hWu4Z032+nqV3vXK=QPJyhZsU3_A@mail.gmail.com/
>
> Guess we will see.
> I expect that the answer is "be reasonable," but that's subjective.
>
> To me, it is easier to look below one line for something in context than it is
> to have to scan several inches to the right and then back to the left (or vice versa).
> Maybe I'm alone in that, but I doubt it.
You are not alone.
Reading left to right is relatively easy but for long line lengths
the eye movement to the next appropriate line is not at all easy.
> It's sort of a locality of vision thing.
Yup.
I think this is not a good patch.
The preferred line length should stay relatively small at 80 and not
allow an entire file to be wrapped to 100.
I'd still prefer a warning when any new identifier is longer than some
length like say 20 characters.
> > 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.
> >
> > Descendants are always substantially shorter than the parent and
>
next prev parent reply other threads:[~2022-01-20 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 21:06 Steven Rostedt
2022-01-19 23:00 ` Randy Dunlap
2022-01-20 0:36 ` Joe Perches [this message]
2022-01-20 9:55 ` Sakari Ailus
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=7e6d37612af05c7c21fc7b06462ccf0da1b8d062.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sakari.ailus@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®