You are correct that we trivially know this information. What would you suggest for the heuristic on not rescheduling? A timer that takes up 500ms out of every 1000 is also something we'd want to kill.
-Matt On Wed, Oct 16, 2013 at 5:52 PM, Anton Bobrov <[email protected]> wrote: > On Wed, Oct 16, 2013 at 05:24:53PM -0700, Matthew Kaniaris wrote: > > Anton, > > > > What do you mean by long running timers? Are you suggesting we look at > the > > running time of the current timer? > > > > -Matt > > Yes, exactly. As far as I understand the implementation dispatcher should > know about > timer's start time and can calculate running time in case of <c-c>. > > -- > -- > 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 a topic in the > Google Groups "vim_dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/vim_dev/-4pqDJfHCsM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- 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.
