Hello, One of the most frustrating things for new Linux users is the "keys are not working out of the box" problem. A part of is it the application keypad mode. It is often turned on from the terminfo/termcap init strings (or when you just hit NumLock twice -- to turn it on and back off). In this mode the keypad (XK_XP_xxx keysyms) generate \eO[npqrvwxy] sequences which are not recognized by the applications, because terminfo gives traditional \e[... sequences for kcuu1, kcud1, kcuf1, kcub1 et al. What is the solution? Removing all traces of \e> and \= from terminfo only helps until I accidentally hit NumLock. Modifying terminfo to list application key sequences instead of the traditional ones will fix some applications but break others (bash; actually readline). I don't think there's an easy way to make all applications understand both variants of the sequences. Currently I have #defined PrivMode_aplKP to (0) in src/rxvt.h as a workaround. Marius Gedminas -- Of course I use Microsoft. Setting up a stable unix network is no challenge ;p
