thac0/vim
1
0
Fork 0
forked from aniani/vim
Code Activity

patch 8.1.2313: debugging where a delay comes from is not easy

Browse Source 
Problem:    Debugging where a delay comes from is not easy.
Solution:   Use different values when calling ui_delay().
This commit is contained in:
Bram Moolenaar
2019-11-17 17:06:33 +01:00
parent 077b9dd354
commit eda1da0c9a
14 changed files with 22 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/normal.c
View File

@@ -1169,8 +1169,8 @@ getcount:
cursor_on();
out_flush();
if (msg_scroll || emsg_on_display)
ui_delay(1000L, TRUE); /* wait at least one second */
ui_delay(3000L, FALSE); /* wait up to three seconds */
ui_delay(1003L, TRUE); /* wait at least one second */
ui_delay(3003L, FALSE); /* wait up to three seconds */
State = save_State;
msg_scroll = FALSE;