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

@@ -2726,9 +2726,9 @@ showmatch(
* available.
*/
if (vim_strchr(p_cpo, CPO_SHOWMATCH) != NULL)
ui_delay(p_mat * 100L, TRUE);
ui_delay(p_mat * 100L + 8, TRUE);
else if (!char_avail())
ui_delay(p_mat * 100L, FALSE);
ui_delay(p_mat * 100L + 9, FALSE);
curwin->w_cursor = save_cursor; /* restore cursor position */
*so = save_so;
*siso = save_siso;