From: Miles Bader <miles@gnu.org>
To: Stefani Seibold <stefani@seibold.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
apw@canonical.com, jschopp@austin.ibm.com, davej@redhat.com
Subject: Re: [PATCH] checkpatch.pl: remove the punch card limit
Date: Thu, 07 Jan 2010 12:07:56 +0900 [thread overview]
Message-ID: <buopr5mobn7.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <1262796984.1011.17.camel@wall-e> (Stefani Seibold's message of "Wed, 06 Jan 2010 17:56:24 +0100")
Stefani Seibold <stefani@seibold.net> writes:
> 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. And it think it make formated source code
> more readable.
>
> For everybody who want know: The 80 column limit of a terminal comes
> from the punch cards, which stored exact 80 characters.
It doesn't really matter where it came from, what matters is whether
people still commonly use 80-column windows or not.
I know people that only ever use one (huuuge) full-screen editor window
with small fonts, and can happily view lines that are 300 characters
long (of course, the right 80% of that window is almost always
completely blank...).
In my case, I use 80-column windows because (1) it allows me to have two
editor/terminal windows side-by-side with a reasonable font-size on a
typical display, (2) it reduces the amount of wasted blank space in
editor/terminal windows that you'd have if you made your windows really
wide just for the very occasional wide line, and (3) it's, well,
standard, or at least as much of a standard as we have, which is useful
when interacting with other people.
Anyway, I think the vague consensus seems to be that it's OK to go over
80 chars in many cases, but that it may be an indicator that some
refactoring is in order....
-Miles
--
80% of success is just showing up. --Woody Allen
next prev parent reply other threads:[~2010-01-07 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 16:56 [PATCH] checkpatch.pl: remove the punch card limit Stefani Seibold
2010-01-07 3:07 ` Miles Bader [this message]
2010-01-07 7:31 ` Stefani Seibold
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=buopr5mobn7.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=davej@redhat.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefani@seibold.net \
/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