From eda1da0c9a8db1400649629117e7d248c07735f7 Mon Sep 17 00:00:00 2001 From: Bram Moolenaar Date: Sun, 17 Nov 2019 17:06:33 +0100 Subject: 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(). --- src/change.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/change.c') diff --git a/src/change.c b/src/change.c index f2542810e..e274d5d98 100644 --- a/src/change.c +++ b/src/change.c @@ -58,7 +58,7 @@ change_warning(int col) ) { out_flush(); - ui_delay(1000L, TRUE); // give the user time to think about it + ui_delay(1002L, TRUE); // give the user time to think about it } curbuf->b_did_warn = TRUE; redraw_cmdline = FALSE; // don't redraw and erase the message @@ -118,7 +118,7 @@ changed(void) if (need_wait_return && emsg_silent == 0) { out_flush(); - ui_delay(2000L, TRUE); + ui_delay(2002L, TRUE); wait_return(TRUE); msg_scroll = save_msg_scroll; } -- cgit v1.2.1