aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/shared.lua
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2023-09-20 06:37:29 +0800
committerGitHub <noreply@github.com>2023-09-20 06:37:29 +0800
commitc4f4c7a356013c6f1e10b7bf239d9e3c4c0c336e (patch)
treefbaa506bdf0387d5bf0430c94ac2d756941aa583 /runtime/lua/vim/shared.lua
parent5a363ccac8ff5889332bafbf68e7e8d20bca316c (diff)
downloadrneovim-c4f4c7a356013c6f1e10b7bf239d9e3c4c0c336e.tar.gz
rneovim-c4f4c7a356013c6f1e10b7bf239d9e3c4c0c336e.tar.bz2
rneovim-c4f4c7a356013c6f1e10b7bf239d9e3c4c0c336e.zip
vim-patch:9.0.1915: r_CTRL-C works differently in visual mode (#25248)
Problem: r_CTRL-C works differently in visual mode Solution: Make r_CTRL-C behave consistent in visual mode in terminal and Windows GUI in visual mode, r CTRL-C behaves strange in Unix like environments. It seems to end visual mode, but still is waiting for few more chars, however it never seems to replace it by any characters and eventually just returns back into normal mode. In contrast in Windows GUI mode, r_CTRL-C replaces in the selected area all characters by a literal CTRL-C. Not sure why it behaves like this. It seems in the Windows GUI, got_int is not set and therefore behaves as if any other normal character has been pressed. So remove the special casing of what happens when got_int is set and make it always behave like in Windows GUI mode. Add a test to verify it always behaves like replacing in the selected area each selected character by a literal CTRL-C. closes: vim/vim#13091 closes: vim/vim#13112 https://github.com/vim/vim/commit/476733f3d06876c7ac105e064108c973a57984d3 Co-authored-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'runtime/lua/vim/shared.lua')
0 files changed, 0 insertions, 0 deletions