aboutsummaryrefslogtreecommitdiff
path: root/test/functional/vimscript/printf_spec.lua
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2025-09-19 08:52:56 +0800
committerzeertzjq <zeertzjq@outlook.com>2025-09-19 09:58:24 +0800
commitdd306bd48abc9d2c68f1a30646b646201c12efc1 (patch)
treebad7f210ecf8f874e6e04356da91b88c0ae28b23 /test/functional/vimscript/printf_spec.lua
parentc2c33249a732ad4df3de1c825bdedc950112500d (diff)
downloadrneovim-dd306bd48abc9d2c68f1a30646b646201c12efc1.tar.gz
rneovim-dd306bd48abc9d2c68f1a30646b646201c12efc1.tar.bz2
rneovim-dd306bd48abc9d2c68f1a30646b646201c12efc1.zip
vim-patch:9.1.1621: flicker in popup menu during cmdline autocompletion
Problem: When the popup menu (PUM) occupies more than half the screen height, it flickers whenever a character is typed or erased. This happens because the PUM is cleared and the screen is redrawn before a new PUM is rendered. The extra redraw between menu updates causes visible flicker. Solution: A complete, non-hacky fix would require removing the CmdlineChanged event from the loop and letting autocompletion manage the process end-to-end. This is because screen redraws after any cmdline change are necessary for other features to work. This change modifies wildtrigger() so that the next typed character defers the screen update instead of redrawing immediately. This removes the intermediate redraw, eliminating flicker and making cmdline autocompletion feel smooth (Girish Palya). Trade-offs: This behavior change in wildtrigger() is tailored specifically for :h cmdline-autocompletion. wildtrigger() now has no general-purpose use outside this scenario. closes: vim/vim#17932 https://github.com/vim/vim/commit/da9c9668931e5c8ee4dc0e430898ad2d80f56862 Use pum_check_clear() instead of update_screen(). Cherry-pick Test_wildtrigger_update_screen() change from patch 9.1.1682. Co-authored-by: Girish Palya <girishji@gmail.com>
Diffstat (limited to 'test/functional/vimscript/printf_spec.lua')
0 files changed, 0 insertions, 0 deletions