[vim/vim] PgUp/PgDn in insert mode rings terminal bell (Issue #19326)
Russell King
rmk92 created an issue (vim/vim#19326)Since upgrading to Debian Trixie, vim has started to ring the terminal bell every time I hit PgUp or PgDn keys while vim is in insert mode.
Previous behaviour was to silently page up or down without ringing the terminal bell.
This very quickly becomes exceedingly annoying, and after some investigation I found that adding the following setting to my ~/.vimrc stopped this behaviour, and made vim usable again:
set belloff=cursor
This evening, I finally got around to (very painfully) bisecting vim, with the bisect crashing out and needing to be restarted several times due to checked-in files being modified by the build. The bisect identified this commit as the culprit for the change in behaviour:
b9f5b95b7bec2414a5a96010514702d99afea18e is the first bad commit
commit b9f5b95b7bec2414a5a96010514702d99afea18e (tag: v9.1.0211)
Author: Luuk van Baal <luuk...@gmail.com>
Date: Tue Mar 26 18:46:45 2024 +0100
patch 9.1.0211: page-wise scrolling does not support smooth-scrolling
Problem: Page-wise scrolling with Ctrl-F/Ctrl-B implements
it's own logic to change the topline and cursor.
In doing so, skipcol is not handled properly for
'smoothscroll', and virtual lines.
Solution: Re-use the logic from Ctrl-E/Ctrl-Y while staying
backward compatible as much as possible.
closes: #14268
Signed-off-by: Luuk van Baal <luuk...@gmail.com>
Signed-off-by: Christian Brabandt <c...@256bit.org>
runtime/doc/options.txt | 6 +-
runtime/doc/version9.txt | 2 +
src/move.c | 377 ++++------------------------------------
src/testdir/test_diffmode.vim | 40 +++--
src/testdir/test_edit.vim | 40 ++---
src/testdir/test_normal.vim | 32 ++--
src/testdir/test_scroll_opt.vim | 24 ++-
src/version.c | 2 +
8 files changed, 121 insertions(+), 402 deletions(-)
~/.vimrc seems not relevant to this; even without it (so using the stock Debian Trixie configuration) exhibits this annoying bell-ringing phenomenon.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.