On Monday, October 14, 2013 9:55:28 AM UTC-5, Ernie Rael wrote: > On 10/14/2013 5:06 AM, Ben Fritz wrote: > > > On Monday, October 14, 2013 5:59:48 AM UTC-5, Michael Henry wrote: > > >> All, > > >> > > >> > > >> > > >> I've been wondering about the use of CTRL-C regarding timers. > > >> > > >> [snip] > > >> > > >> > > > I think this is a valid concern. > > > > > > I'm not exactly sure how this works now, I remember discussion about a list > > of canceled timers. Perhaps a single invocation could be canceled allowing > > this list to be displayed, then a second CTRL-C would be required (with the > > list displayed) to actually cancel all future invocations as well. > > > > > An implication of this is that "randomly" a timer event may not be run, > > or only partially run. That could make plugins using timers pretty > > tricky to write.
Well I didn't mention it, but I was actually envisioning this message would block timers or other commands until dismissed somehow. Otherwise a timer or mapping could easily do :redraw! and the message would be gone anyway. I press CTRL-C very infrequently. I'd be willing to give it a try first without such a feature and see how often I accidentally interrupt timers. We get a message if timers are cancelled, yes? Is it possible to restart them somehow or are you just out of luck if this happens? -- -- 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.
