>>If there is collaboration at all, developers need to use the same rule >>or the same coding style in the project anyway. At least the same coding >>style should be retained within one module. I see this to be a >>reasonable rule.
>And with tabs, people are a lot more flexible. Absolutely. And as for leading indentation, whether tabs or spaces makes no difference to me, as I convert everything to tabs and ts=8 anyway. >:D That being said, if I have lots of nesting going on and too many levels means I start the line halfway across the screen, I'll stick a modeline at the very end of the file that'll specify ts=4 or even ts=2, depending how much of a rat's nest it happens to be. As for hairy alignments to pretty-up an overly long conditional, etc., hey, if a few spaces can't preserve the alignment someone wants, then just indent it to the next tablevel and leave the rest of us alone. I object to someone "committing" a file to his/her own preferred style via endless leading spaces with ts=3 or something, just so he/she can have a nicely-aligned table of conditionals in an if() statement. It's an *editor*, not a word-processor. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
