Peter Hodge <[EMAIL PROTECTED]> wrote on 2006.07.19 09:32:47: > I can see your point and it is concerning that the colour change is enough to > force you to go back to Vim 6.4, but Bram (or any software package > author) must > reserve privileges to change things and make them the default, otherwise > everyone gets a Vim 7.0 which behaves exactly like 6.4 and 70% of > the user base > doesn't have the time or knowledge to find and activate the new features. I > regularly confront this issue as I write the PHP syntax as I must decided > whether to A) make a feature ON by default and frustrate lots of people; or B) > make a feature OFF by default so that no one gets annoyed, but risk that many > people will miss out on that feature because they don't know how to > turn it on. > > regards, > Peter
Hi Peter, My opinion is: if I can live with the previous version, then that's it, and I certainly can live with the new version without the new features "turn on" by default. If there is something I cannot live with in the previous version, or if I feel I must have the new feature, then I will try to find how to turn it on. Any way, Vim is not an editor which people can learn without any effort, do you think those who are willing to spend time to learn Vim do not want to learn the new features they DO want? If I do really want the feature, I will try to find how to turn it on, otherwise, I'd rather the authors just leave it OFF. For example, after installed Vim 7.0 I found the cursor movement become unacceptably slow, I spend too much time, finally I found its due to the "matchparen" plugin, and I spend much more time to find how to disable it in an elegant way. ---- if the new "feature" are OFF by default, my life would have been much easier. Again, after installed Vim 7.0, the VisVim behaves strange, and have a high chance not opening the specified file at all. I don't know where the problem is, so I have to use Vim 6.4 with VS.
