Richard Hartmann 写道:
> You are cheating by trying to align across several levels of logical nesting.
First, I'm not cheating, it *is* the real scenario in our everyday 
programming.

> It's obvious that there is no flexible method of alignment in that situation,
> today. You would need a meta-tab or something similar if you wanted
> to achieve this in a text interface.
Yes there is one method: use spaces.

> I still maintain that this is not needed in the real world as maintaining
> perfect alignment of behind-code comments is not practicable with
> more than two or three level of indentation, anyway. _Especially_
> with sw=8 which you seem to prefer.
No, I don't say sw=8, I'd say ts=8 and sw=(what ever you want). i.e. 
don't rely on hard tab to do indent, tabs are used to create tables, not 
indent. Using spaces to do indent isn't the right way either, but in 
fixed-width-font world especially in programming, spaces are the most 
natural way for indent.

> You definition of reasonable differs from mine.
> The case you constructed serves as justification to force everyone
> touching your code to adhere to your rules. Not a nice thing to do
> at best, actively harming collaboration at best.
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.

> Point in case, the Perl guidelines suggest sw=4 using soft tabs.
> Forcing them to use sw=8 is just plain unfair.
Again, I'm saying ts=8 and sw=(what ever you want). And that is 
*recommended* by official vim documents. If someone claims that spaces 
waste more bytes than hard tabs, he can :set noet, which will change all 
leading 8 spaces into hard tabs and there isn't too much bytes wasted by 
the space character.

> 
> Richard

Pan, Shi Zhu

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to