> We also have :syntax on, filetype plugin on and so on. So I think it
> makes perfectly sense to be able to turn timers off globally using e.g.
> :timers off
I still think that timers should have a string ID generated on plugin side.
Since plugins will 99% of time reuse one ID for one task it allows collecting
stats I described earlier. And with ID :timers off may then be reduced to
set ignoretimers=*
(where 'ignoretimers' setting has 'wildignore'-like syntax and obvious purpose)
if you think it is good to have some way to ignore timers: this way you can
target specific plugin only. Like I will use after/ directory and :au!/:unmap
if I see some too intrusive CursorHold event/mapping (though more likely I will
remove the plugin) and definitely not 'eventignore' that will hurt all plugins.
Note that all of :au!/:unmap/set eventignore/:filetype off/:syntax off/etc rely
on good will of plugin authors: only laziness may prevent them from coding
self-recovering in case user has disabled parts of the functionality.
--
--
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.
