mirrors/neovim
1
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2025-09-26 04:58:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

vim-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().
eda1da0c9a
This commit is contained in:
Jan Edmund Lazo
2021-04-13 00:26:34 -04:00
parent 94b10d25da
commit b8c3bb6790
9 changed files with 19 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/nvim/change.c
View File

@@ -68,7 +68,7 @@ void change_warning(int col)
(void)msg_end();
if (msg_silent == 0 && !silent_mode && ui_active()) {
ui_flush();
os_delay(1000L, true); // give the user time to think about it
os_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
@@ -109,7 +109,7 @@ void changed(void)
// and don't let the emsg() set msg_scroll.
if (need_wait_return && emsg_silent == 0) {
ui_flush();
os_delay(2000L, true);
os_delay(2002L, true);
wait_return(true);
msg_scroll = save_msg_scroll;
} else {