From: Simon Farnsworth <simon@farnz.org.uk>
To: Alexander Clouter <alex@digriz.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch.pl: remove the 80 charactes punch card limit
Date: Mon, 01 Feb 2010 10:53:47 +0000 [thread overview]
Message-ID: <4B66B2BB.9050909@farnz.org.uk> (raw)
In-Reply-To: <17r837-m29.ln1@chipmunk.wormnet.eu>
Alexander Clouter wrote:
> Andi Kleen <andi@firstfloor.org> wrote:
>>> The time of 80 characters punch card and terminals are over, so i would
>>> be a good thing to set the line length limit to 120. Every display today
>>> should be able handle this.
>>>
>>> Signed-off-by: Stefani Seibold <stefani@seibold.net>
>> Full Ack!
>>
> NACK Attack!
>
> There is a reason Knuth only put so many words on a line with TeX.
>
If you're going to cite Knuth as a reason for the 80 character per line
limit, you should understand the difference between ribbon length and
line length.
While there are good reasons to constrain the number of characters in a
ribbon, and to prohibit too much of a shift in indentation between two
neighbouring lines, there's no particularly strong readability reason to
limit a line to 80 characters.
Thus, assuming that maintainers read the patches they're sent, and apply
a bit of common sense (insisting on sensibly sized ribbons, and getting
grouchy about deep indentation), an 80 character line length limit isn't
needed.
--
Simon
next prev parent reply other threads:[~2010-02-01 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 13:09 [PATCH] checkpatch.pl: remove the 80 charactes punch card limit Stefani Seibold
2010-01-27 18:07 ` Joel Schopp
2010-01-27 19:01 ` David Daney
2010-01-27 20:31 ` Joel Schopp
2010-01-27 20:42 ` David Daney
2010-01-27 21:36 ` Stefani Seibold
2010-01-28 15:54 ` Andi Kleen
2010-01-28 16:39 ` Alexander Clouter
2010-01-29 5:19 ` tytso
2010-01-29 18:49 ` Joe Perches
2010-02-01 10:53 ` Simon Farnsworth [this message]
2010-01-28 17:58 ` David Daney
2010-01-28 16:01 ` Krzysztof Halasa
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=4B66B2BB.9050909@farnz.org.uk \
--to=simon@farnz.org.uk \
--cc=alex@digriz.org.uk \
--cc=linux-kernel@vger.kernel.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