Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of hyperhacker@gmail.com
 designates 74.125.82.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F0A8936.70208@rowe-clan.net>
References: <4F061C80.5040005@rowe-clan.net>
 <D86D3EEE-40CF-4833-9881-77500463341F@jaguNET.com>
 <4F09DAB5.90606@apache.org> <4F0A8936.70208@rowe-clan.net>
From: HyperHacker <hyperhacker@gmail.com>
Date: Mon, 9 Jan 2012 01:04:25 -0700
Message-ID: 
 <CA+rfA1RXLugHbKCWL1oZD4i-15ccNDcAQq3bA5-SyaB=AfDCjQ@mail.gmail.com>
Subject: Re: Style rule change?
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Jan 8, 2012 at 23:29, William A. Rowe Jr. <wrowe@rowe-clan.net> wro=
te:
> On 1/8/2012 12:04 PM, Guenter Knauf wrote:
>> on the other side: I've asked me already often if we shouldnt increase t=
he maxchar/line; I
>> believe that would in many cases greatly increase readability ...
>> and honestly: who the heck does nowadays work on a 80-line terminal??
>
> Frequently on unix and windows. =A0I haven't yet committed the time to
> try working on a headless windows server 2008, however :) =A0My text
> editor windows all default to 81 cols to avoid just this issue.
>
>> isn't that a relic inherited from stone-time? I would be fine with f.e. =
110 or 120 chars/line.
>
> Is a limit even appropriate anymore? =A0On what basis? =A0132 chars is on=
e
> standard that could be applied. =A0Perhaps a precommit filter to avoid
> issues in the future?

I can nicely fit 3 editor windows at 80 columns on my screen. It's very han=
dy.

--=20
Sent from my toaster.