From: Jari Aalto <jari.aalto@cante•net>
To: git@vger•kernel.org
Subject: Re: On Tabs and Spaces
Date: Thu, 18 Oct 2007 11:19:48 +0300 [thread overview]
Message-ID: <abqgltqz.fsf@blue.sea.net> (raw)
In-Reply-To: 200710180031.54819.dmitry.torokhov@gmail.com
* Thu 2007-10-18 Dmitry Torokhov <dmitry.torokhov@gmail•com>
* Message-Id: 200710180031.54819.dmitry.torokhov@gmail•com
> On Wednesday 17 October 2007, Jari Aalto wrote:
>
>> - Any editor will display the text written in "all spaces"
>> 100 % the same. Regradless of any viewer or editor used.
>>
>> But the same is not true with text that uses tabs (because you
>> really can't know what options the editor is preset / user set /
>> regarding the treatment of tabs).
>>
>> The score is 1 - 0 for "all spaces" in this contest.
>>
>
> How about this - I like tabs because when you removing it you
> need to hit Backspace just once and don't have to strain your
> eyes figuring out "Did I delete enough? Does it line up now?"
First I must say that you're right. From user's perspective some things
are convenient and some things not so convenient; it depends:
a) select an editor where these are no-issues
b) use an editor that can be configured so that these are no-issues
c) use the current editor and live by its limitations
I do not speak for any particular project here, just from a general
perspective[1]:
A project policy QA enforces standards so that everybody can expect
things to work the same way. The common denominator from view
perspective (person A, B, C, D ... loads the text into a editor) is
"all spaces". Similarly if code is post processed, all tools can
expect that there are no surprises (it's all spaces, no combination
of spaces and tabs).
The effect of a project policy in general is to enforce standards that
may not necessary match everybody's preferences[2].
Jari
[1] 99 % of the projects do not use Kernel's 8-wide indentation
convention. In all seriously taken editors, the TAB-key is configurable
to move to specific positions; so called "tab stops". Therefore "hit
TAB-key to insert tab character" does not usually apply in coding
context. In coding, the TAB-key is used to control the indentation
level, which is a measure defined in Project policy (coding style).
[2]
The tabs vs spaces issue is simular to those of:
- Starting curly brace placement policy: at EOL, or at separate line
- Identifier naming policy: camelCase vs. dash_names
--
Welcome to FOSS revolution: we fix and modify until it shines
next prev parent reply other threads:[~2007-10-18 8:21 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 6:45 On Tabs and Spaces Michael Witten
2007-10-16 7:04 ` Shawn O. Pearce
2007-10-16 7:27 ` Michael Witten
2007-10-16 17:20 ` Andreas Ericsson
2007-10-16 17:40 ` Sam Ravnborg
2007-10-16 23:09 ` Petr Baudis
2007-10-17 3:41 ` David
2007-10-17 11:32 ` Andy Parkins
2007-10-16 8:30 ` Adam Piatyszek
2007-10-16 9:04 ` Lars Hjemli
2007-10-16 10:16 ` Adam Piatyszek
2007-10-16 15:26 ` Jeffrey C. Ollie
2007-10-16 15:51 ` Michael Witten
2007-10-16 17:06 ` Jari Aalto
2007-10-16 19:20 ` Linus Torvalds
2007-10-16 19:36 ` Mike Hommey
2007-10-16 19:47 ` Linus Torvalds
2007-10-16 19:51 ` Linus Torvalds
2007-10-16 20:32 ` Matthieu Moy
2007-10-16 20:18 ` Tom Tobin
2007-10-16 23:05 ` Linus Torvalds
2007-10-16 23:51 ` Christer Weinigel
2007-10-17 0:45 ` Linus Torvalds
2007-10-17 3:08 ` Michael Witten
2007-10-17 3:29 ` Linus Torvalds
2007-10-17 7:17 ` Luke Lu
2007-10-17 9:09 ` Michael Witten
2007-10-17 10:03 ` Luke Lu
2007-10-17 10:21 ` Nikolai Weibull
2007-10-17 11:23 ` Michael Witten
2007-10-17 22:02 ` Jari Aalto
2007-10-17 22:36 ` Andreas Ericsson
2007-10-17 23:38 ` Jari Aalto
2007-10-18 4:31 ` Dmitry Torokhov
2007-10-18 8:19 ` Jari Aalto [this message]
2007-10-18 11:34 ` Petr Baudis
2007-10-18 11:39 ` Nikolai Weibull
2007-10-22 3:39 ` Miles Bader
2007-10-18 7:15 ` David Kågedal
2007-10-18 5:42 ` Mike Hommey
2007-10-18 10:36 ` Jari Aalto
2007-10-17 15:53 ` Linus Torvalds
2007-10-17 18:05 ` Johannes Schindelin
2007-10-17 18:25 ` Tom Tobin
2007-10-17 18:54 ` Linus Torvalds
2007-10-17 19:33 ` Tom Tobin
2007-10-17 19:44 ` Linus Torvalds
2007-10-17 19:48 ` Nicolas Pitre
2007-10-17 19:52 ` Josh England
2007-10-17 19:53 ` Linus Torvalds
2007-10-17 21:21 ` Christer Weinigel
2007-10-17 22:03 ` Linus Torvalds
2007-10-18 6:25 ` David Kastrup
2007-10-17 22:11 ` Johannes Schindelin
2007-10-17 23:17 ` Christer Weinigel
2007-10-17 23:44 ` Johannes Schindelin
2007-10-18 0:31 ` Christer Weinigel
2007-10-18 6:02 ` Andreas Ericsson
2007-10-18 7:12 ` David Kågedal
2007-10-17 23:53 ` Linus Torvalds
2007-10-17 20:31 ` David Kastrup
2007-10-17 21:08 ` Johannes Schindelin
2007-10-17 19:47 ` Jan Wielemaker
2007-10-18 0:32 ` Jeff King
2007-10-18 0:59 ` Linus Torvalds
2007-10-18 2:45 ` Jeff King
2007-10-18 3:03 ` david
2007-10-18 3:00 ` Jeff King
2007-10-18 3:32 ` Linus Torvalds
2007-10-18 4:17 ` Linus Torvalds
2007-10-18 3:13 ` Linus Torvalds
2007-10-18 3:23 ` Jeff King
2007-10-18 4:41 ` [PATCH] Add a message explaining that automatic GC is about to start koreth
2007-10-18 4:44 ` Steven Grimm
2007-10-18 5:01 ` Jeff King
2007-10-18 5:11 ` Shawn O. Pearce
2007-10-18 13:52 ` Brian Gernhardt
2007-10-18 14:16 ` Steven Grimm
2007-10-18 18:08 ` Jeff King
2007-10-19 0:16 ` Shawn O. Pearce
2007-10-19 1:12 ` [PATCH] git-gc: improve wording of --auto notification Jeff King
2007-10-19 1:24 ` Shawn O. Pearce
2007-10-19 1:26 ` Jeff King
2007-10-18 14:21 ` [PATCH] Add a message explaining that automatic GC is about to start Nicolas Pitre
2007-10-18 4:52 ` On Tabs and Spaces Nicolas Pitre
2007-10-18 4:54 ` Jeff King
2007-10-18 4:55 ` Jeff King
2007-10-17 16:08 ` David Kastrup
2007-10-17 17:44 ` Nicolas Pitre
2007-10-17 19:52 ` David Kastrup
2007-10-17 17:51 ` Sean
2007-10-17 5:56 ` David Kastrup
2007-10-16 20:56 ` Sam Ravnborg
2007-10-18 3:31 ` Paul Wankadia
2007-10-18 4:22 ` Linus Torvalds
2007-10-18 4:36 ` Dmitry Potapov
2007-10-16 17:23 ` Andreas Ericsson
2007-10-16 18:34 ` Jan-Benedict Glaw
2007-10-16 18:51 ` Andreas Ericsson
2007-10-20 13:54 ` Robin Rosenberg
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=abqgltqz.fsf@blue.sea.net \
--to=jari.aalto@cante$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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