Change in behaviour in pageup/pagedown keys?
- iTerm2 version: Build 0.20210501_111349-adhoc (due to testing for #9580)
- OS version: macOS 10.14.6
- Attach com.googlecode.iterm2.plist here (drag-drop from finder into this window)
Since I started to use this version of iterm2, I noticed the following problem.
In my editor (joe), previously PgUp/PgDown caused the editor to scroll. I used shift-PgUp and shift-PgDown if I wanted to go back in the terminal scrollback history. This is still the case with iTerm2 3.4.6.
However with this adhoc build, PgUp/PgDown and shift-PgUp/shift-PgDown both go back through the terminal scrollback history; I can no longer scroll the file I am editing :-(
For comparison: in Apple's Terminal, PgUp/PgDown does the scrollback, and shift-PgUp/shift-PgDown scrolls the editor (which is the opposite way round to how I want it). This makes me think that joe itself isn't the problem.
On the other hand, using 'vi' in the iterm2 adhoc build I see the behaviour I expect: PgUp/PgDown scrolls the vi editor buffer, with shift it scrolls the scrollbank window.
I recently did a "brew upgrade", and although joe itself doesn't appear to have changed:
$ ls -l /usr/local/Cellar/joe/*
total 296
-rw-r--r-- 1 brian admin 18092 10 Jan 2018 COPYING
-rw-r--r-- 1 brian admin 62379 10 Jan 2018 ChangeLog
-rw-r--r-- 1 brian admin 591 20 Jan 2018 INSTALL_RECEIPT.json
-rw-r--r-- 1 brian admin 49099 10 Jan 2018 NEWS.md
-rw-r--r-- 1 brian admin 9285 10 Jan 2018 README.md
drwxr-xr-x 7 brian admin 224 10 Jan 2018 bin
drwxr-xr-x 3 brian admin 96 10 Jan 2018 etc
drwxr-xr-x 6 brian admin 192 10 Jan 2018 share
$ ls -l /usr/local/Cellar/joe/4.6/bin/
total 1240
lrwxr-xr-x 1 brian admin 3 10 Jan 2018 jmacs -> joe
-r-xr-xr-x 1 brian admin 630828 10 Jan 2018 joe
lrwxr-xr-x 1 brian admin 3 10 Jan 2018 jpico -> joe
lrwxr-xr-x 1 brian admin 3 10 Jan 2018 jstar -> joe
lrwxr-xr-x 1 brian admin 3 10 Jan 2018 rjoe -> joe
...I suppose it's possible that some library it depends on has. However, given that reverting to iTerm2 3.4.6 makes the problem go away, I'm pretty sure this is an iTerm issue.