all repos — st @ 73879c172943928542225cdc975b3b7e2449ddc0

st (suckless terminal) config

Adding an FAQ entry for the keypad handling.

Thanks "Roberto E. Vargas Caballero" <k0ga@shike2.com>!
Christoph Lohmann 20h@r-36.net
commit

73879c172943928542225cdc975b3b7e2449ddc0

parent

5facd29f75401891fbac9c83d64c684bdb8f7c39

1 files changed, 35 insertions(+), 0 deletions(-)

jump to
M FAQFAQ

@@ -37,4 +37,39 @@

[0] http://en.wikipedia.org/wiki/GNU_Screen [1] http://en.wikipedia.org/wiki/Tmux -- +Why doesn't the Del key work in some programs? + +Taken from the terminfo manpage: + + If the terminal has a keypad that transmits codes when the keys + are pressed, this information can be given. Note that it is not + possible to handle terminals where the keypad only works in + local (this applies, for example, to the unshifted HP 2621 keys). + If the keypad can be set to transmit or not transmit, tive these + codes as smkx and rmkx. Otherwise the keypad is assumed to + always transmit. + +In the st case smkx=\E[?1h\E= and rmkx=\E[?1l\E>, so it is mandatory that +applications which want to test against keypad keys, have to send these +sequences. + +But buggy applications like bash and irssi for example don't do this. A fast +solution for them is to use the following command: + + $ echo ^[?1h^[= >/dev/tty + +or + $ echo $(tput smkx) >/dev/tty + +In the case of bash it is using readline, which has a different not in its +manpage: + + enable-keypad (Off) + When set to On, readline will try to enable the + application keypad when it is called. Some systems + need this to enable arrow keys. + +Adding this option to your .inputrc will fix the keypad problem for all +applications using readline. +--