From 21f160746a4b406f84311a64fff96c1bd52f23c9 Mon Sep 17 00:00:00 2001
From: Jan Edmund Lazo <jan.lazo@mail.utoronto.ca>
Date: Sun, 26 May 2019 19:39:38 -0400
Subject: vim-patch:8.1.0020: cannot tell whether a register is executing or
 recording

Problem:    Cannot tell whether a register is being used for executing or
            recording.
Solution:   Add reg_executing() and reg_recording(). (Hirohito Higashi,
            closes vim/vim#2745)  Rename the global variables for consistency.  Store
            the register name in reg_executing.
https://github.com/vim/vim/commit/0b6d911e5de1a1c10a23d4c2ee1b0275c474a2dd
---
 src/nvim/fileio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/nvim/fileio.c')

diff --git a/src/nvim/fileio.c b/src/nvim/fileio.c
index f97ae8778d..e2b77d9605 100644
--- a/src/nvim/fileio.c
+++ b/src/nvim/fileio.c
@@ -6677,7 +6677,7 @@ bool trigger_cursorhold(void) FUNC_ATTR_PURE FUNC_ATTR_WARN_UNUSED_RESULT
 
   if (!did_cursorhold
       && has_cursorhold()
-      && !Recording
+      && reg_recording == 0
       && typebuf.tb_len == 0
       && !ins_compl_active()
       ) {
-- 
cgit