aniani/vim
0
0
Fork 1
mirror of https://github.com/vim/vim.git synced 2025-09-30 04:44:14 -04:00
Code Activity

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

Browse Source 
Problem:    Not clear why SafeState and SafeStateAgain are not triggered.
Solution:   Add log statements.
This commit is contained in:
Bram Moolenaar
2019-09-17 20:28:38 +02:00
parent 0e57dd859e
commit 37d1807a80
4 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/main.c
View File

@@ -1061,6 +1061,11 @@ may_trigger_safestate(int safe)
&& 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 @@ may_trigger_safestate(int safe)
void
state_no_longer_safe(void)
{
if (was_safe)
ch_log(NULL, "safe state reset");
was_safe = FALSE;
}
@@ -1082,10 +1089,15 @@ state_no_longer_safe(void)
* 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");
}