Bram Moolenaar wrote the following on 17.10.2011 18:50 Hello Bram, Tony, Ben and Ingo
-- <snip> -- > I'm not sure if this is going to be a good solution. -- <snip> -- Yes agreed my short hand solution does not work out as others have already explained. > What we could do is change $VIMRUNTIME/syntax/synload.vim and the place > where indent files are loaded. But again, doing this for some scripts > and not all might just cause confusion. > > It might be better to have a test to run all syntax files, indent > scripts, etc in compatible mode and check if any of them fails. Sorry I am not sure if i can assist with that. What do you think about Bens idea with "setscript"? If i sum up the current consensus no matter which solution will take place, the solution will take place inside the runtime files which means potentially several of them will need to be changed anyway. That means we have the occasion to fix them one for all. Several other critical options are already mentioned. Can we collect them all? Which ones are missing? We then could have a vimscript template (in runtimesfiles in the wiki or where ever, or even a ':StartNewVimScript') that can be used as a starter to hopefully prevent the loops for maintainers as described by Ben. Does that sound reasonably? 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
