From: Felix Domke <tmbinc@elitedvb.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Indention - why spaces?
Date: Mon, 30 Dec 2002 21:43:19 +0100 [thread overview]
Message-ID: <3E10AFE7.6030301@elitedvb.net> (raw)
In-Reply-To: <3E109EF1.5040901@WirelessNetworksInc.com>
hi,
> This problem is as old as the typewriter itself. The trouble is that
> a Tab character doesn't have a fixed size - some set it to 3
> characters wide, some to 4 some to 8, or whatever.
>
> The 'indent' program was written a couple of decades ago, to pretty
> print C code. It has a 'GNU' standard, but I'm not aware of a 'Linux'
> standard. Anyhoo, the only way to prevent indentation wars is to use
> spaces, not tabs and to set 'diff' to ignore white space when
> comparing files...
Anyhow, sorry, i really can't understand that. What could be more
"indention war preventing" that letting everybody use his own indention
width?
There are two main aspects of *not* using tabs:
- editors mess them up. but: use an *editor*. not a word processor.
kernel source's line endings are \n, not \r\n. some (windows) editors
mess them up. and nobody cares (and that's ok that way. nobody WANTS to
use an editor which messes up so simple things).
some editors don't show tabs. well. this leads to a mixup of tabs <->
spaces. but if you really fear about this, just use an editor which
supports showing tabs. joe doesn't show spaces (by default?), but i
never missed that, for example.
- aligning. well, just use spaces for aligning, tabs for indention. two
different things. two different characters.
TAB characters simply *have* no assigned width. that's the reason for
them. they are not a macro for 3/4/8 spaces.
not using spaces, in my eyes, just *takes* a possibility to
platform-independant format sourcecode on the given screensize. it gives
you nothing.
and as they might be some pitfalls (wrong aligning etc.), you can still
set the tabwidth to the one of the author. in that case, you didn't win
anything by using tabs, but you didn't loose either.
again, i was just *wondering* why everybody is using spaces, and still,
i can't find a good reason for that. if anybody shows me that, i'll
maybe start using spaces (again).
felix
next prev parent reply other threads:[~2002-12-30 20:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.f9m4suv.e6ubgf@ifi.uio.no>
2002-12-30 3:33 ` Indention - why spaces? Russ Allbery
2002-12-30 3:43 ` Larry McVoy
2002-12-30 3:47 ` john slee
2002-12-30 4:26 ` Russ Allbery
2002-12-30 23:20 ` Mark Mielke
2002-12-30 12:28 ` Wichert Akkerman
2002-12-30 12:49 ` John Bradford
2002-12-30 12:57 ` Wichert Akkerman
2002-12-30 13:12 ` Rik van Riel
2002-12-30 13:16 ` Russell King
2002-12-30 13:17 ` Dave Jones
2002-12-30 18:53 ` Emiliano Gabrielli
2002-12-30 19:00 ` Arnaldo Carvalho de Melo
2002-12-30 19:30 ` Herman Oosthuysen
2002-12-30 9:42 ` Zac Hansen
2002-12-30 20:43 ` Felix Domke [this message]
2002-12-30 23:26 ` Mark Mielke
2002-12-31 1:02 ` Wichert Akkerman
2002-12-30 23:55 ` Herman Oosthuysen
2002-12-31 2:20 ` Anthony J. Breeds-Taurima
2002-12-31 9:47 ` Christoph Hellwig
[not found] ` <mailman.1041274740.23755.linux-kernel2news@redhat.com>
2002-12-31 5:28 ` Pete Zaitcev
2002-12-31 6:04 ` Larry McVoy
2002-12-30 16:12 ` Larry McVoy
2002-12-31 22:43 Heater, Daniel (IndSys, GEFanuc, VMIC)
-- strict thread matches above, loose matches on Subject: below --
2002-12-31 17:21 Roberto Peon
2002-12-30 2:29 Felix Domke
2002-12-30 11:28 ` Christoph Hellwig
2002-12-31 8:55 ` Tomas Szepe
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=3E10AFE7.6030301@elitedvb.net \
--to=tmbinc@elitedvb.net \
--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.