where CSI is ESC followed by left bracket ([) on a 7-bit connection or decimal 155 on an 8-bit connection, and SS3 is ESC followed by O (uppercase letter O) on a 7-bit connection and decimal 143 on an 8-bit connection. How does the cursor keypad mode change?
SET TERMINAL ARROW-KEYS { CURSOR, APPLICATION } So why do the arrow keys not work in Lynx? Or, in general, in any particular application: • Because the application expects the keypad to be in one mode when it is in the other mode. This is a deficiency on the part of the application. Applications should never ASSUME which mode the cursor keypad is in, but rather, they should PUT the keypad in the desired mode, or else they should accept arrow-key codes from either mode. Workaround: tell Kermit to SET TERM ARROW CURSOR (or APPLICATION). • Because of a terminal-type mismatch. Lynx, in particular, does not seem to use the termcap database (it uses only terminfo), and so therefore might not understand Kermit’s VT220 or VT320 terminal type (this kind of confusion typically occurs when a terminal type is in the termcap database but not the terminfo one, and therefore works with EMACS or vi, but not with Lynx). Solution: tell Kermit to SET TERM TYPE VT100 and also tell the host your terminal t
Related Questions
- where CSI is ESC followed by left bracket ([) on a 7-bit connection or decimal 155 on an 8-bit connection, and SS3 is ESC followed by O (uppercase letter O) on a 7-bit connection and decimal 143 on an 8-bit connection. How does the cursor keypad mode change?
- I have followed step-by-step instructions in User Manual, however, still cannot establish TCP connection. Any suggestions?
- I followed the guidelines but still I have no bluetooth connection?
