Mercurial > vim
comparison src/ui.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 | 9e6d5a4abb1c |
children | df141c730008 |
comparison
equal
deleted
inserted
replaced
18641:b288ef9327ac | 18642:bbea1f108187 |
---|---|
530 * cancel the delay if a key is hit. | 530 * cancel the delay if a key is hit. |
531 */ | 531 */ |
532 void | 532 void |
533 ui_delay(long msec, int ignoreinput) | 533 ui_delay(long msec, int ignoreinput) |
534 { | 534 { |
535 #ifdef FEAT_JOB_CHANNEL | |
536 ch_log(NULL, "ui_delay(%ld)", msec); | |
537 #endif | |
535 #ifdef FEAT_GUI | 538 #ifdef FEAT_GUI |
536 if (gui.in_use && !ignoreinput) | 539 if (gui.in_use && !ignoreinput) |
537 gui_wait_for_chars(msec, typebuf.tb_change_cnt); | 540 gui_wait_for_chars(msec, typebuf.tb_change_cnt); |
538 else | 541 else |
539 #endif | 542 #endif |