allan grossman writes: > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Tried to navigate a text file in nano with PgUp and PgDown keys. > > * What was the outcome of this action? > > Navigation is successful if using a terminal ssh session, > using a putty session PgUp and PgDown keys don't work.
I can't reproduce anything that sounds like this, albeit on a setup rather different from yours (my own PuTTY 0.81 build, with default settings; bullseye=oldstable, and hence a rather old nano, 5.4-2+deb11u3; it looks like nano have been doing things with their keybindings rather recently, which may be relevant). What is the terminal type within the PuTTY session? (echo $TERM) Have you changed any PuTTY settings from the defaults? One that might be particularly worth looking at is 'The Function keys and keypad' on the Keyboard panel. The settings 'VT400' and 'SCO' cause non-default sequences to be sent for PgUp/PgDn (although on my system, with TERM=xterm, nano accepts all the sequences PuTTY can send). What exactly happens when you press PgUp or PgDn when using PuTTY? Does anything get inserted into the file you're editing with nano? Is this nano-specific? Do PgUp/PgDn work in other programs, such as 'less'? Computer Enthusiastic writes: > I found that rebuilding the putty package with compiler optimisation > disabled seems to fix the problem. It would be quite surprising for this to make a difference. Were you actually experiencing exactly the same symptom as the original reporter (as far as it's possible to tell)? If so, I wonder if it's possible that your local rebuild isn't using the same saved settings as whatever version you used that showed the problem.
