9 Commits

Author	SHA1	Message	Date
Justin M. Keyes	e7de3b5f84	test/timer_spec.lua: Relax expected count. ... Test sometimes fails on AppVeyor (Windows). 300/50=6, but there could be environment factors that miss the timer interval on the "edges". timer_start() does not have such a hard requirement.	2017-01-19 14:46:29 +01:00
Björn Linse	719dae2e01	events: allow event processing in getchar() ... this is consistent with vim, and is necessary for plugins that implement their own input modes using "getchar()" and still want to do async event processing.	2016-10-15 09:50:59 +02:00
Björn Linse	f282b8ecac	tests: don't ignore highlights in various tests	2016-08-14 21:53:02 +02:00
Björn Linse	0a51d26b33	timers: do not crash after processing events in the handler	2016-08-10 11:22:28 +02:00
Björn Linse	5c754a2d22	timers: make repeat=0 work one-shot (consistent with vim)	2016-06-29 18:57:18 +02:00
Björn Linse	2c39e0b03f	timers: make timers work with zero timeout	2016-06-29 18:57:18 +02:00
ZyX	ff470bb853	functests: Check logs in lua code ... It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.	2016-06-10 21:50:49 +03:00
Björn Linse	5cc87d4dab	cmdline: Redraw the cmdline after processing events ... vim-patch:7.4.1603 TODO(bfredl): if we allow events in HITRETURN and ASKMORE states, we need to add the necessary redraws as well.	2016-05-24 22:11:37 +02:00
Björn Linse	61e8adb25e	eval: implement timers. vim-patch: 7.4.1578, 7.4.1831 ... For the moment, timers are triggered during sleep, but not in wait-for-input modes, like press-RETURN or f_getchar()	2016-05-24 22:08:56 +02:00