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

@@ -1761,7 +1761,7 @@ report_default_term(char_u *term)
screen_start(); /* don't know where cursor is now */
out_flush();
if (!is_not_a_term())
ui_delay(2000L, TRUE);
ui_delay(2007L, TRUE);
}
}
@@ -2810,7 +2810,7 @@ term_get_winpos(int *x, int *y, varnumber_T timeout)
*y = winpos_y;
return OK;
}
ui_delay(10, FALSE);
ui_delay(10L, FALSE);
}
/* Do not reset "did_request_winpos", if we timed out the response might
* still come later and we must consume it. */