Thilo Six wrote the following on 17.10.2011 12:17 Hello Bram,
> Additionally to already identified bogus files, where 'cpo-=C' is expected > there > are ones which actually expect an environment which has 'cpo-=l' set! > > IMHO those need to be fixed, too. > > Actually those 'cpo-=l' bugs are not as obvious. -- <snip> -- After thinking a little bit more about this issue I would like to ask you Bram a question about this. Currently the approach seems to be that a vim script has to create a sane environment on its own. Maybe we should change that paradigm to: When a vim script wants a insane environment it has to create it on its own. That means basically that we change vim to parse each file from $VIMRUNTIME as if it would have been preceded with 'set cpo&vim'. This basically leads to changing cpo from 'global only' to 'script local only'. The advantage seems to be, that vim would actually behave as script maintainers silently expect. Now the question Bram: What do you think about this? If we can't have the above (for what ever reason), can we require that each and every runtimefile has to handle cpo correctly on it's own, please? Regards, -- bye Thilo 4096R/0xC70B1A8F 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
