-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Lieb wrote: > Micah Cowan wrote: >> Try adding the line: > >> terminfocap screen* ks@:ke@ > >> to your final destination host's ~/.screenrc or /etc/screenrc, and see >> if that makes a difference in (freshly started) screen sessions. > > I added the line: > > termcapinfo screen* ks@:ke@ > > to ~/.screenrc on the final host and the numpad now works normally when > in a nested screen session. (I assume that's what you meant in your > last email.)
Here's some additional information about what's going on. I installed pterm (which is basically the PuTTY terminal split off from the ssh stuff), and was able to reproduce these symptoms. In particular, doing $ tput smkx in pterm made the number keypad appear to stop working, and $ tput rmkx would restore it. Since screen sends smkx at startup, it's not clear to me why the first screen doesn't exhibit the problem (it doesn't for me, either, but does in a nested screen); perhaps another sequence that is sent when TERM is xterm but not when it's screen, cancels the effect. Note that the number pad _is_ actually doing something. If you try pressing numpad keys while running "cat", you'll see things like: ^[Ow^[Oq etc. These correspond to what DEC-style terminals would send for the numpad when in keypad-transmit mode (smkx). I note that ncurses' official terminfo descriptions has an entry for putty, and that it lacks definitions for smkx/rmkx. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. Maintainer of GNU Wget and GNU Teseq http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmu98kACgkQ7M8hyUobTrHbswCfShkXMs+/4Qw8Ui4biVkcYxKy yyYAnAnhVy3uYYLWFOdiuRhsZ5nADT7p =WqrX -----END PGP SIGNATURE----- _______________________________________________ screen-users mailing list screen-users@gnu.org http://lists.gnu.org/mailman/listinfo/screen-users
