This is usually a symptom of a broken terminfo description for whatever
terminal you happen to use screen from (specifically, the "ti/te"
capabilities). A workaround would probably be to place
termcapinfo <foo> ti@:te@
in your ~/.screenrc; where <foo> is the name your terminal identifies
itself as (via the $TERM value it sets). Note that this change will
typically also prevent screen from restoring the terminal's previous
contents from before it was run.
If it is a broken terminfo description, then you should probably identify for
us:
- what is the terminal emulator program you're using/running screen inside?
- what does it identify itself as, with $TERM?
- is it a laptop keyboard, where the "keypad" overlaps the normal keys (in
this case, the workaround may be your only option, as there are some keyboards
that don't work well with terminals' "application modes").
Are you using PuTTY? PuTTY by default identifies itself as "xterm" or
"xterm-color", even though its numpad sequences are not compatible with
xterm's. Please be sure that your $TERM setting is consistent with the
actual terminal screen is running under.
** Changed in: screen (Ubuntu)
Status: New => Incomplete
** Changed in: screen (Ubuntu)
Assignee: (unassigned) => greenmoss (ktyubuntu)
--
A subset of input keys temporarily stop working
https://bugs.launchpad.net/bugs/349636
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
