All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Tabs, spaces, indent and 80 character lines
Date: Sun, 24 Feb 2008 16:40:49 +0100	[thread overview]
Message-ID: <47C19001.7010609@student.ltu.se> (raw)
In-Reply-To: <m3ejb2bdxx.fsf@maximus.localdomain>

Krzysztof Halasa wrote:
> Richard Knutsson <ricknu-0@student.ltu.se> writes:
>
>   
>> Why hinder a developer who prefer
>> 2, 4, 6 or any other != 8 width?
>>     
>
> I guess we could use tabs only at the line start, for indentation
> only. Rather hard to implement, most text editors can't do that yet.
>   
You mean for split lines? Hopefully there won't be that many, so there 
is just to delete the tabs it added and replace it with spaces.
>   
>> By only using tabs as indents, and
>> changing the CodeStyle to be something like "maximum 80
>> characters-wide lines, with a tab-setting of 8 spaces",
>>     
>
> This changes nothing.
>   
Exactly! But then we can remove the "we use 8 wide tabs in the kernel" 
in CodeStyle.
>   
>> that is
>> possible + easier to write code-checkers [2].
>>     
>
> I doubt it.
>   
Easier to write code-checkers? OK, maybe not. Just that I got hit by 
this problem at a time when I wrote a simple checker (don't remember its 
purpose).
>   
>> Or are we really that concerned about the disk-space? ;)
>>     
>
> Unpacked sources will be much bigger with not tabs, sure.
>   
Without no tabs at all, you mean? Don't want to think about that 
scenario, but with this suggestion, I would estimate maybe 0,5 - 1% bigger.

Thanks for your input


  parent reply	other threads:[~2008-02-24 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  0:48 Tabs, spaces, indent and 80 character lines Richard Knutsson
2008-02-24 14:56 ` Krzysztof Halasa
2008-02-24 15:01   ` Miles Bader
2008-02-25 22:13     ` Richard Knutsson
2008-02-26  2:00       ` Jan Engelhardt
2008-02-26 15:50         ` Krzysztof Halasa
2008-02-26 22:03         ` Richard Knutsson
2008-02-24 15:40   ` Richard Knutsson [this message]
2008-02-24 16:15     ` Benny Halevy
2008-02-25 21:40       ` Richard Knutsson
2008-02-26  0:47         ` Benny Halevy
2008-02-24 17:36     ` Krzysztof Halasa
2008-02-25 21:56       ` Richard Knutsson

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=47C19001.7010609@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.