Mercurial > vim
diff src/term.c @ 18642:bbea1f108187 v8.1.2313
patch 8.1.2313: debugging where a delay comes from is not easy
Commit: https://github.com/vim/vim/commit/eda1da0c9a8db1400649629117e7d248c07735f7
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 17 17:06:33 2019 +0100
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().
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sun, 17 Nov 2019 17:15:04 +0100 |
| parents | 0388e1991ec5 |
| children | fd95d4dbeb37 |
line wrap: on
line diff
--- 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, varnumbe *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. */