From: Benny Halevy <bhalevy@panasas.com>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Tabs, spaces, indent and 80 character lines
Date: Mon, 25 Feb 2008 16:47:53 -0800 [thread overview]
Message-ID: <47C361B9.7010304@panasas.com> (raw)
In-Reply-To: <47C335D9.3010803@student.ltu.se>
On Feb. 25, 2008, 13:40 -0800, Richard Knutsson <ricknu-0@student.ltu.se> wrote:
> Benny Halevy wrote:
>> On Feb. 24, 2008, 7:40 -0800, Richard Knutsson <ricknu-0@student.ltu.se> wrote:
>>
>>> 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.
>>>
>> IMO, tabs SHOULD be used for syntactic indentation and spaces for
>> decoration purpose only. I.e. a line should start with a number of tabs
>> equal to its nesting level and after that only spaces should be used.
>> for example, the following code
>>
>> for (i = 0; i < n; i++) printk("a very long format string", some, parameters);
>>
>> should be formatted like this:
>>
>> <tabs...>for (i = 0; i < n; i++)
>> <tabs...><tab>printk("a very long format string",
>> <tabs...><tab> some, parameters);
>>
>> this will show exactly right regardless of your editor's tab expansion setting
>> as long as you use fixed-width fonts - where the screen width of the space character
>> is equal to all other characters. Once you start using tabs instead of spaces
>> to push text right so it appears exactly below some other text on the line above
>> you make a dependency on *your* editor's tab expansion policy and that's not very
>> considerate for folks who prefer a different one.
>>
> Don't know what to say more then: Yup! :)
>
> But the CodeStyle-document and checkpatch.pl does not agree with that.
>
I know :(
If there's enough interest I can take a stab at seeing what it'd
take to implement such a check in checkpatch.pl
Benny
next prev parent reply other threads:[~2008-02-26 0:48 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
2008-02-24 16:15 ` Benny Halevy
2008-02-25 21:40 ` Richard Knutsson
2008-02-26 0:47 ` Benny Halevy [this message]
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=47C361B9.7010304@panasas.com \
--to=bhalevy@panasas.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=ricknu-0@student.ltu.se \
/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.