News for hackers. Stuff that matters.
Re:Elastic Tab Stops: A Better Way to Indent and Align Code by nihilocrat on Wednesday October 15, 2008 @11:03PM (#334094)
I remember reading this several years ago. It's not something that is 100% implemented by configuring emacs or vi properly: read the entire article slowly.

I'm surprised I haven't heard any Python coders piping up. We pick spaces or tabs, and stick with it; otherwise, our code doesn't run. Mixing tabs and spaces is pure evil.

I prefer spaces, because a space is a space and will display as exactly one space in any text editor.

Re:Elastic Tab Stops: A Better Way to Indent and Align Code by njharman on Thursday October 16, 2008 @09:07AM (#334394)
> I'm surprised I haven't heard any Python coders piping up.

Because either indentation is a non-issue for you or you don't use Python.

Any decent editor solves this problem to the 98-99% mark. There's lots more interesting things to do than dick around with that 1-2%

Python forces you to keep your indentation correct and sane so it's never so whacked you need special tools to deal with it.

Proper indenting is subconscious like other languages ';' at end of line or parens around expressions in if/for. That is when it isn't automatically handled by your editor...

Re:Elastic Tab Stops: A Better Way to Indent and Align Code by DougBTX on Thursday October 16, 2008 @01:00PM (#334639)
Well, any editor with fixed width fonts, which the author of the article would like to move away from.
Re:Elastic Tab Stops: A Better Way to Indent and Align Code by arthurk on Thursday October 16, 2008 @04:18AM (#334243)
Even if you use tabs, the Python compiler will convert a tab to 8 spaces internally.