![]() ![]() ![]() You can also do things like tput khome | hexdump -C if you know the terminfo capability names for the keys you are interested in. If the above is too cryptic, try infocmp -L Here you can see that, if TERM were set to xterm, this server would expect to receive ESC [ 1 ~ when Home is pressed ( khome) # Reconstructed via infocmp from file: /usr/share/terminfo/x/xterm You can look at what is expected for other values of TERM $ infocmp -I xterm Khome=\E[H means that the server expects to receive three characters ESC [ H when you press Home. # Reconstructed via infocmp from file: /usr/share/terminfo/a/ansi Type infocmp -I to see what your computer is expecting. The problem is the value of the TERM environment variable does not match the configured terminal characteristics - specifically the "Home and End keys" and "Function keys and keypad" settings. I ran od -c on both ssh console, and pressed esc, they gave the same output. in this malfunctioning ssh console, I press esc, it shows ^[. When in a correctly working ssh console, I press esc, it should show nothing. ![]() Here I will show why I think esc is mismapping: It seems that the mismapping of ESC is the root cause. After reading the manual of putty, I successfully made backspace key to work, but still have troubles about ESC, arrows, home and end, and F1- F12 keys. I noticed that it's about keyboard config in putty. But I've met a strange problem about keyboard behaviors on putty console. I'm using putty on win7 as client, to log into ssh on a debian server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |