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/main.c

diff --git a/src/main.c b/src/main.c
index 42aa990..ff3d234 100644
--- a/src/main.c
+++ b/src/main.c
@@ -1061,6 +1061,11 @@
 		    && scriptin[curscript] == NULL
 		    && !global_busy;
 
+    if (was_safe != is_safe)
+	// Only log when the state changes, otherwise it happens at nearly
+	// every key stroke.
+	ch_log(NULL, is_safe ? "Start triggering SafeState"
+						: "Stop triggering SafeState");
     if (is_safe)
 	apply_autocmds(EVENT_SAFESTATE, NULL, NULL, FALSE, curbuf);
     was_safe = is_safe;
@@ -1074,6 +1079,8 @@
     void
 state_no_longer_safe(void)
 {
+    if (was_safe)
+	ch_log(NULL, "safe state reset");
     was_safe = FALSE;
 }
 
@@ -1082,10 +1089,15 @@
  * SafeStateAgain, if it was safe when starting to wait for a character.
  */
     void
-leave_unsafe_state(void)
+may_trigger_safestateagain(void)
 {
     if (was_safe)
+    {
+	ch_log(NULL, "Leaving unsafe area, triggering SafeStateAgain");
 	apply_autocmds(EVENT_SAFESTATEAGAIN, NULL, NULL, FALSE, curbuf);
+    }
+    else
+	ch_log(NULL, "Leaving unsafe area, not triggering SafeStateAgain");
 }