The team decides what the indentation style should be
Not on any project I run. "Discussions" about indentation style lead to some of the most unpleasant, passive-aggressive, time-wasting and downright unproductive meetings I've ever attended. There's always at least one or two people who are unwilling to compromise on what they consider to be the "best" style (as you can see by scrolling around this discussion).
The reason I tend to prefer the IDE default (for languages where it's a no-brainer to use the IDE, like Java) is because it requires the least effort to get right. There's always some bonehead who joins the project later, doesn't read the style guide, and starts committing using the default settings. If your project standard is the default settings, this is fine. On projects where you wasted around 8 hours determining that the indent should be four spaces and there should be a rigid right-column margin of 80 chars, this means that someone will check out the source, open it in Eclipse, and start committing changes indented with tabs. The IDE guys already had all those arguments about style, and they almost certainly have more collective experience than you. Use that experience, don't waste your life reinventing the wheel.
Have the team lead pick a simple, easily followed style, and allow a certain amount of leeway - as the saying goes foolish consistency is the hobgoblin of little minds. The point is to make the code easier to understand, and if there are occasions when deviating from the style guide improves this, do it.
Spend the time you would have wasted arguing about tabs or spaces creating a culture of discussion about what makes for clearer, more understandable code. Rules of thumb like "if you find yourself with the urge to comment a particular stretch of code, consider that you might just write the code more clearly".