On Sunday, October 20, 2013 10:39:28 PM UTC-5, Andre Sihera wrote: > > > Furthermore, a timer being effectively an "interrupt", there should be > > an extra test > > case that executes underneath the timer when it fires that can be shown > > to produce > > a known result when the timer interrupt returns, hence showing that the > > execution > > of commands within a timer has no unknown side-effects on the > > interrupted code. >
If I understand correctly, the timer runs in the "idle" loop of Vim, so it should not ever interrupt any code running outside the timer. -- -- 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.
