[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Keypad bindings for num pad
From: |
Benno Schulenberg |
Subject: |
Re: Keypad bindings for num pad |
Date: |
Mon, 25 Apr 2022 11:10:23 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 |
Op 25-04-2022 om 02:48 schreef cookieguru@gmail.com:
> I'm on Ubuntu 20.04.4 and recently upgraded from nano 2.8 to 4.8.
There is no nano-2.8. I guess you upgraded from Bionic (Ubuntu 18.04),
from nano-2.9.3.
> My /etc/nanorc file had "set rebindkeypad" and that was the only way I could
> use the num pad correctly in nano. Since that upgrade that directive no
> longer exists and I'm no longer able to type numbers on the num pad inside
> nano. Everything works fine in bash.
What terminal do you use? And what is the output of 'env | grep TERM'?
Does nano work fine with keypad keys when you use xterm instead?
> I can launch nano with -K and the num pad works as expected. But surely there
> is a better way to fix this than with an alias in my bashrc.
Did you try reading the manual? Run 'man nano' and search for -K. See
that its long option is --rawsequences. So, try using 'set rawsequences'
in your .nanorc.
> I noticed that in 9c1c6c18a[1] this was no longer declared a bug but a
> problem with ncurses.
Not at all -- it's *not* a problem with ncurses, it's a problem with your
terminal: it is producing escape sequences that do not match the TERM that
it sets. When you run 'nano --ignorerc' and then type M-V KP7 (where KP7
is the 7 key on the keypad while NumLock is on), what sequence is shown?
Benno
OpenPGP_signature
Description: OpenPGP digital signature