... > Maybe control-c should cancel intervals. As you mentioned, this would let > users save stuff and restart vim. At worse, plugins would be dumped into > an inconsistent state that could cause more harm. Also, canceling internal > callbacks is quite opaque to users. I don't see any great options for > dealing with runaway plugins. > > > What I typically see if lots of users have many plugins installed. It is very easy to forget what was installed last that could be leading to "strange" problems in Vim. Anything running asynchronously I assume could easily fall under this category.
So yes, I believe an option or something to turn off asynchronous execution would be a great idea, as it would be one more step people on this list could suggest to see if the "symptom" goes away and allows the user to narrow their search to find the offending code. My 2 cents. David -- -- 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.
