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

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

View File

@@ -2373,10 +2373,11 @@ showmatch(
* brief pause, unless 'm' is present in 'cpo' and a character is
* available.
*/
if (vim_strchr(p_cpo, CPO_SHOWMATCH) != NULL)
os_delay(p_mat * 100L, true);
else if (!char_avail())
os_delay(p_mat * 100L, false);
if (vim_strchr(p_cpo, CPO_SHOWMATCH) != NULL) {
os_delay(p_mat * 100L + 8, true);
} else if (!char_avail()) {
os_delay(p_mat * 100L + 9, false);
}
curwin->w_cursor = save_cursor; // restore cursor position
*so = save_so;
*siso = save_siso;