Open a file with at least 2 lines and try to use PGUP on the first line, you should end up on a line strictly below.
image.png (view on web)Additional information:
As far as I understand #17331 and the related pull requests since its closure, you are not aware of this issue and there wasn't related commit since 9.2.0250.
Note that the issue does not happen via SSH.
seems to have introduced the issue.
As a temporary workaround Termux vim package termux/termux-packages#29170 reverts above commit.
It should keep being on the first line.
9.2.0250 (9.2.0272 with 1fe0d1e reverted also has the issue)
Operating system: LineageOS 23.2 (Fairphone 4)
Terminal: Termux (https://github.com/termux/termux-app/tree/3f0dec3574a6617ff7ff0b78d30b29cfffd71b20)
Value of $TERM: xterm-256color
Shell: bash 5.3.9
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
ping @AstroSnail
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
This seems to be a Termux bug to me. I have alerted them here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
closing then here. Thanks @AstroSnail
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Until the new release of Termux, users of Termux should set noxtermcodes in their vimrc, because it had a bug in its implementation of the 'xtermcodes' feature that swapped PGUP and PGDN.
(cc @A4-Tacks @vrtareg who made duplicate issues)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()