diff options
author | Bram Moolenaar <Bram@vim.org> | 2019-11-17 17:06:33 +0100 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2019-11-17 17:06:33 +0100 |
commit | eda1da0c9a8db1400649629117e7d248c07735f7 (patch) | |
tree | b5357f17e49a2bc1cd71a44895b6d0621124605a /src/term.c | |
parent | 077b9dd3541339a23ade0cc6a23e804ee39312c5 (diff) | |
download | vim-git-eda1da0c9a8db1400649629117e7d248c07735f7.tar.gz |
patch 8.1.2313: debugging where a delay comes from is not easyv8.1.2313
Problem: Debugging where a delay comes from is not easy.
Solution: Use different values when calling ui_delay().
Diffstat (limited to 'src/term.c')
-rw-r--r-- | src/term.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/term.c b/src/term.c index 94552a631..5b8901ed1 100644 --- a/src/term.c +++ b/src/term.c @@ -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. */ |