> 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
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
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).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/