From b8c3bb67904794e9f45bdc4546aa43009f43c592 Mon Sep 17 00:00:00 2001
From: Jan Edmund Lazo <jan.lazo@mail.utoronto.ca>
Date: Tue, 13 Apr 2021 00:26:34 -0400
Subject: vim-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().
https://github.com/vim/vim/commit/eda1da0c9a8db1400649629117e7d248c07735f7
---
 src/nvim/os/time.c | 1 +
 1 file changed, 1 insertion(+)

(limited to 'src/nvim/os/time.c')

diff --git a/src/nvim/os/time.c b/src/nvim/os/time.c
index e7e0dc4013..9ea74716aa 100644
--- a/src/nvim/os/time.c
+++ b/src/nvim/os/time.c
@@ -62,6 +62,7 @@ uint64_t os_now(void)
 /// @param ignoreinput If true, only SIGINT (CTRL-C) can interrupt.
 void os_delay(uint64_t ms, bool ignoreinput)
 {
+  DLOG("%" PRIu64 " ms", ms);
   if (ignoreinput) {
     if (ms > INT_MAX) {
       ms = INT_MAX;
-- 
cgit