Brett Stahlman 写道: > with the existence of legacy code? i.e., people who edit legacy code > and write new code want to be able to have the same settings for both? > If so, I understand the argument, but it just seems to me that mixing > tabs and spaces for leading indent was a solution to a problem > (inability to change tabstop from 8 spaces), Yes, that is what I'm stating, for programmers who have to read all kind of source codes, he will have to change the tab size from time to time to read those who uses hard tabs with non-standard size. life would be much easier if those sources use only spaces for indent.
Most text files uses tab-size as 8 and it is very common that a Linux software source file contains not only C, thus it is heretical not to keep ts=8. For Makefiles, assemblers, vim help files, and many script languages of configuration files they have a standard tab-size=8, those are not legacy code and ts=8 works perfect. Only in C and C++ world there is a divergence, yes it is easy to change the tab-size only for C, but if we must set ts=4 in 25% of C codes in project X and ts=6 in 35% of C codes and ts=8 in the other 40% C codes of project X things are really in a mess. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
