commit 37d1807a801d5296f00b3ac85a38b26cfe6de55c
author Bram Moolenaar <Bram@vim.org> Tue Sep 17 20:28:38 2019 +0200
committer Bram Moolenaar <Bram@vim.org> Tue Sep 17 20:28:38 2019 +0200
tree d44d74c0e9c2c696ec593b1156f9efab811bafa9
parent 0e57dd859ecb1e8a3b91509d2f4343e839340eb8

patch 8.1.2048: not clear why SafeState and SafeStateAgain are not triggered

Problem:    Not clear why SafeState and SafeStateAgain are not triggered.
Solution:   Add log statements.

src/getchar.c

diff --git a/src/getchar.c b/src/getchar.c
index 3f3c6bc..93d0d64 100644
--- a/src/getchar.c
+++ b/src/getchar.c
@@ -2103,7 +2103,7 @@
     // When not nested we'll go back to waiting for a typed character.  If it
     // was safe before then this triggers a SafeStateAgain autocommand event.
     if (entered == 1)
-	leave_unsafe_state();
+	may_trigger_safestateagain();
 
     may_garbage_collect = save_may_garbage_collect;