void foo() {
__callToFooBar(arg1,
__………….longArg2,
__………….arg3,
__………….veryLongArg4
__);
}

1) Use tabs to indent your code (and let people decide if they prefer to see tabs as 4-spaces or 8-spaces, I hate reading code in 2-spaces). It’s better in terms of semantics, memory space and user configuration. And it’s easier to (un)indent code with just TAB/backspace.

2) Use spaces when you align your code, that way it won’t break, Here I’ll show you, paste this in a code editor:
(__ = tab, . = space)

class Foo(object):
__def foobar(self):
____var1………..=.value1
____long_var2……=.value2
____very_long_var3.=.value3

In most worth while editors, we can control the *visual* depth of the hard tab while keeping the actual character count down.

The 20 bytes you consider saving leads me to believe that you have not worked on a big project. Tens of thousands of lines of code using spaces over hard tabs is A LOT of wasted space.

Lets also consider the memory the editor requires to open the files. More characters per file = more memory to the editor.

Yes, you get some benefits with spaces like making sure that parameters can line up across multiple lines. But this is a worthwhile loss for the consistent lining up of real indenting.

Do you still wrap your code at line 80? Seems like a waste of that big monitor…

I personally don’t have a problem with either, I’ll use whatever is recommended by the language I am using. So far the only language that’s given me some indentation problems is Haskell.