zeertzjq ac353e87ae vim-patch:9.0.2075: TextChangedI may not always trigger (#25808) ...

Problem:  TextChangedI may not always trigger
Solution: trigger it in more cases: for insert/
          append/change operations, and when
          opening a new line,

fixes: vim/vim#13367
closes: vim/vim#13375

4bca4897a1

Co-authored-by: Christian Brabandt <cb@256bit.org>

2023-10-28 10:42:18 +08:00

..

autocmd_oldtest_spec.lua

…

autocmd_spec.lua

…

bufenter_spec.lua

…

bufmodifiedset_spec.lua

…

cmdline_spec.lua

…

cursorhold_spec.lua

…

cursormoved_spec.lua

…

dirchanged_spec.lua

…

filetype_spec.lua

…

focus_spec.lua

…

modechanged_spec.lua

…

recording_spec.lua

…

safestate_spec.lua

test: add some tests for SafeState autocommand

2023-08-21 14:16:16 +08:00

searchwrapped_spec.lua

…

show_spec.lua

…

signal_spec.lua

…

tabclose_spec.lua

…

tabnew_spec.lua

…

tabnewentered_spec.lua

fix(ui): trigger TabNewEntered after split new tab

2023-10-07 16:40:57 +08:00

termxx_spec.lua

fix(terminal): assign channel to terminal earlier (#25771)

2023-10-25 09:59:02 +08:00

textchanged_spec.lua

vim-patch:9.0.2075: TextChangedI may not always trigger (#25808)

2023-10-28 10:42:18 +08:00

textyankpost_spec.lua

…

win_scrolled_resized_spec.lua

test(winscrolled): make sure floating window is drawn (#25639)

2023-10-14 20:09:49 +08:00