On Wed, Aug 13, 2008 at 04:58:21AM +0200, Bram Moolenaar wrote: > Now that I look at this again, I think we should not change this. I'll > add a remark at the documentation for -C that startup scripts and > plugins may change the option and you end up with 'nocompatible' anyway. > > If there are plugins that change the 'compatible' option, we should > consider that a bug. Even changing it temporarily and restoring it has > side effects.
I agree that plugins shouldn't change it, but I see valid uses for startup scripts to change it. > I rather have a clear problem than an unpredictable solution. If a user specifies -N/-C on the command-line, this overrides their 'compatible' setting from the startup scripts. It's fairly typical configuration precedence. I do agree that the other proposed fix (preventing the startup scripts from changing 'compatible' if -N/-C was specified) is more straight-forward from the user perspective since it only affects 'compatible' and not the related settings that they may explicitly set. Obviously, you have the final say but I think being able to explicitly override the config-file behavior via -N/-C is a desireable behavior and follows the current spirit of the documentation. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
