From: Kay Sievers <kay.sievers@vrfy.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 80 column line limit?
Date: Thu, 5 Jan 2006 22:14:38 +0100 [thread overview]
Message-ID: <20060105211438.GA1408@vrfy.org> (raw)
In-Reply-To: <84144f020601050532l56c15be1i4938a84f6c212960@mail.gmail.com>
On Thu, Jan 05, 2006 at 03:32:28PM +0200, Pekka Enberg wrote:
> On 1/5/06, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > Can't we relax the 80 column line rule to something more comfortable?
> > These days descriptive variable/function names are much more valuable,
> > I think.
>
> I don't see the point, really. If your nesting is within reasonable
> limits, long names are usually not a problem.
Well, it always feels silly, to line wrap manually like in this patch:
http://lkml.org/lkml/mbox/2005/12/2/219
And sometimes it would just be nice to have "len" called "buflen"
or whatever, but that makes things even worse with the 80's rule. :)
I just wanted to do some whitespace cleanup and add named prototypes
to include/linux/device.h but a lot of lines are already exceeding
80 columns and wrapping the lines would make the file even more
unreadable, that's why I was asking. :)
> And your nesting is too deep, it should be fixed.
It's not about nesting, if that's the reason, the number of tabs
should get a maximum specified instead.
> Out of curiosity, what limit do you think
> would work better to you?
Normal 80, but if it makes sense 120, then usually the editor will line
wrap, which is in most cases better to read than starting lines at
column 60.
Thanks,
Kay
next prev parent reply other threads:[~2006-01-05 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 13:02 80 column line limit? Kay Sievers
2006-01-05 13:27 ` Jesper Juhl
[not found] ` <20060105154330.da1016fc.grundig@teleline.es>
2006-01-05 22:27 ` Jesper Juhl
2006-01-05 13:32 ` Pekka Enberg
2006-01-05 21:14 ` Kay Sievers [this message]
2006-01-05 22:03 ` Jan Engelhardt
2006-01-06 5:52 ` Willy Tarreau
2006-01-06 7:09 ` Jan Engelhardt
2006-01-05 13:43 ` Giuliano Pochini
2006-01-05 23:02 ` Alistair John Strachan
2006-01-06 1:34 ` Jim Nance
2006-01-06 7:12 ` Jan Engelhardt
[not found] <5rD2D-xs-11@gated-at.bofh.it>
2006-01-05 18:08 ` Bodo Eggert
2006-01-06 7:14 ` Jan Engelhardt
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=20060105211438.GA1408@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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