From: Willy Tarreau <willy@w.ods.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: 80 column line limit?
Date: Fri, 6 Jan 2006 06:52:08 +0100 [thread overview]
Message-ID: <20060106055208.GE7142@w.ods.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0601052301270.27662@yvahk01.tjqt.qr>
On Thu, Jan 05, 2006 at 11:03:09PM +0100, Jan Engelhardt wrote:
> >> 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.
> >
> Or we could have the tab width lowered, but I doubt
> Linus would accept that :)
In fact, one tab could be lowered, it's the first one. Nearly all code
has at least this tab which is not very useful and would not affect
readability if reduced to 2 or 4. But it will be difficult to maintain
a variable tab width, not to mention the alignment problem on the
second tab.
BTW, if 80 is not enough, simply consider that one tab is exactly one
character ( '\011' ) and you will be able to put more, but I doubt
your code will be accepted ;-)
Willy
next prev parent reply other threads:[~2006-01-06 5:52 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
2006-01-05 22:03 ` Jan Engelhardt
2006-01-06 5:52 ` Willy Tarreau [this message]
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=20060106055208.GE7142@w.ods.org \
--to=willy@w.ods.org \
--cc=jengelh@linux01.gwdg.de \
--cc=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