thac0/vim
1
0
Fork 0
forked from aniani/vim
Code Activity

patch 9.0.2031: TextChangedI may be triggered by non-insert mode change

Browse Source 
Problem:  `TextChangedI` can trigger on entering Insert mode if there
          was previously a change not in Insert mode.
Solution: Make it trigger only when text is actually changed in Insert
          mode.

closes: #13265
closes: #13338

Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com>
This commit is contained in:
Evgeni Chasnovski
2023-10-15 09:59:00 +02:00
committed by Christian Brabandt
parent 47510f3d65
commit d7ae263af8
3 changed files with 23 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/edit.c
View File

@@ -174,6 +174,9 @@ edit(
return FALSE;
}
ins_compl_clear(); // clear stuff for CTRL-X mode
// Reset Changedtick_i, so that TextChangedI will only be triggered for stuff
// from insert mode
curbuf->b_last_changedtick_i = CHANGEDTICK(curbuf);
/*
* Trigger InsertEnter autocommands. Do not do this for "r<CR>" or "grx".
@@ -840,6 +843,7 @@ doESCkey:
if (cmdchar != 'r' && cmdchar != 'v' && c != Ctrl_C)
ins_apply_autocmds(EVENT_INSERTLEAVE);
did_cursorhold = FALSE;
curbuf->b_last_changedtick = CHANGEDTICK(curbuf);
return (c == Ctrl_O);
}
continue;