[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using the numpad in nested screens

From: Micah Cowan
Subject: Re: Using the numpad in nested screens
Date: Wed, 04 Mar 2009 13:51:05 -0800
User-agent: Thunderbird (X11/20090105)

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,
  $ 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:


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
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


reply via email to

[Prev in Thread] Current Thread [Next in Thread]