On Tue, 16 Oct 2007, Jari Aalto wrote: > * Tue 2007-10-16 Michael Witten <mfwitten AT MIT.EDU> > > > > However, 8 spaces per tab is a lot of wasted > > information to be bandying about. > > Spaces are guaranteed to interpreted correctly in all environments. TABs > are the source of too many problems. No. Tabs are 8 spaces wide. Live with it. It's the only sane solution. The fact is, people do mix the two. No ifs, buts or maybes about it. Even in the absense of any actual *spaces*, the size of a tab matters, since you can - and do - have two separately indented things (the initial indentation, and then things like comments being indented separately). The only sane solution is the one the kernel and git have always used: tabs are 8 spaces wide, and anybody who disagrees can go screw themselves. If you don't have 8-character tabs, you *will* get odd indentation. And no, the answer is not to say "don't use tabs at all" and replace them by spaces. The answer is *also* not "tabs are just for initial code indents", because not only will most sane editors never even show the difference, it's simply not how people work. So such a rule about invisible things doesn't work. People who want to be contrary, and have a 2-character-wide tab only have themselves to blame. It's THEIR problem, not somethign that is even worth trying to address. If there are problems with people having small screens, that is damn well not about TAB, it's about code being way too deeply indented, and smaller indents are absolutely *not* the answer - they are part of the damn problem to begin with. The fact that some projects have encouraged bad coding style and *insane* tab values is not a git problem. We should teach people to do *better*, not become worse just because others have done idiotic things. Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
