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/change.c
View File

@@ -58,7 +58,7 @@ change_warning(int col)
)
{
out_flush();
ui_delay(1000L, TRUE); // give the user time to think about it
ui_delay(1002L, TRUE); // give the user time to think about it
}
curbuf->b_did_warn = TRUE;
redraw_cmdline = FALSE; // don't redraw and erase the message
@@ -118,7 +118,7 @@ changed(void)
if (need_wait_return && emsg_silent == 0)
{
out_flush();
ui_delay(2000L, TRUE);
ui_delay(2002L, TRUE);
wait_return(TRUE);
msg_scroll = save_msg_scroll;
}