On Monday, October 14, 2013 2:45:26 AM UTC-5, Andre Sihera wrote: > On 14/10/13 12:02, kans wrote: > > > Andre, > > > I agree with Ben and Zyx. If you don't want to deal with timers, don't > > install plugins that use them. There can be no expectation that any plugin > > will work if you disable its timers. If a plugin is more trouble than its > > worth, uninstall the plugin. Moreover, any interval can be canceled with > > ctrl-c and it won't be rescheduled (so this should never be an issue). > > > > There is another solution which is far simpler than any code fix > > or additional command. > > > > Simply, to make sure that no plug-in or filetype extension that > > uses a timer ever makes it into the standard ViM install packages. >
I agree that no timer functionality of any standard Vim plugins should be enabled by default in a new Vim install. But I'd accept some timer-based features in the standard plugins if they were opt-in. Kind of like matchit is distributed with Vim but you need to take an extra step to actually use it. > > > That way, the system will be at its most robust and predictable > > after installation as it is currently. If the user installs then a plug-in > > themselves and things start to go wrong they know exactly which > > plug-in needs to be uninstalled. Agree. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
