[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <465C50FC.8050604@austin.ibm.com>
Date: Tue, 29 May 2007 11:12:44 -0500
From: Joel Schopp <jschopp@...tin.ibm.com>
To: Andy Whitcroft <apw@...dowen.org>
CC: Jan Engelhardt <jengelh@...ux01.gwdg.de>,
Andrew Morton <akpm@...l.org>,
Randy Dunlap <rdunlap@...otime.net>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] add a trivial patch style checker
>>> + if(!($prevline=~/\/\*\*/) && length($lineforcounting) > 80){
>> Actually, I think this should be "> 79" (after stripping a .diff's
>> control column), since the cursor may move to the 81th column when
>> editing an 80-col line - which is what we want to avoid, no?
>
> 80 tends to work for me because of that "if on 80 then don't wrap until
> there is another character" behaviour of most terminals. Anyone else
> with a firm opinion.
I think 80 is good. What the specific number is does not matter much, we all have
screens wider than 80 characters. The point is just to have a number that prevents
really long lines and prevents people from indenting too many levels past our minds
ability to keep up. We've already all been coding to 80, and it happens to be a nice
round number we can all remember and love. The only reason I see to select 79 is
that prime numbers are generally cooler than other numbers.
-Joel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists