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/ui.c | |
parent | 077b9dd3541339a23ade0cc6a23e804ee39312c5 (diff) |
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/ui.c')
-rw-r--r-- | src/ui.c | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -532,6 +532,9 @@ ui_char_avail(void) void ui_delay(long msec, int ignoreinput) { +#ifdef FEAT_JOB_CHANNEL + ch_log(NULL, "ui_delay(%ld)", msec); +#endif #ifdef FEAT_GUI if (gui.in_use && !ignoreinput) gui_wait_for_chars(msec, typebuf.tb_change_cnt); |