Date: Wed, 17 May 95 10:33:32 MDT From: terry@cs.weber.edu (Terry Lambert) To: nox@jelal.hb.north.de (Juergen Lock) Cc: ache@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com Subject: Re: Changed information for PR misc/409 Message-ID: <9505171633.AA26049@cs.weber.edu> In-Reply-To: <9505152004.AA00267@jelal.hb.north.de> from "Juergen Lock" at May 15, 95 10:04:28 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > On all VT100-like (xterm included) keypad not supposed to generate numbers > > in keypad-active mode, but generates arrows instead > > So that means NumLock isn't supposed to work? with NumLock off > i get arrows, with NumLock on i get different escape sequences > unknown to vi. > > or should i just :map them to digits... The NumLock key switches the keypad between edit key mode and numeric key mode. So it will send escape sequences for up/down/left/right/home/end/pgup/pgdown or it will send the current keypad mode values. If yout termcap 'ti' string tells it to turn on keypad mode, it will, and the current keypad mode values will be escape sequences; otherwise, the current keypad mode values will be digits and the other characte that the keypad normally sends (+/-/del/enter). So the NumLock has squat to do with whether the keypad values sent are numeric or escape sequences, it has only to do with switching between the keypad values (whatever they are) and the edit values (an IBM extension when the original keyboards weren't 101 keys). If you want numeric instead of escape sequence values for the keypad values, then you will have to remove the terminal initialization sequence that requests the escape sequence values. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9505171633.AA26049>