I guess same thing that happens to any application that sets weird modes. You should use 'reset' command which just emits escape code to reset terminal and terminal emulator hopefully sets everything back correctly.
Well, from what I've read all alphanumeric can be typed just fine, they go as is to terminal, problem is with special keys that some of them emit escape sequences that confuse shell or combinations of those.
But not to trust what I just read I've installed kitty and tested it and you can type in the "reset" just fine.
I hit a bit of a problem with "Entering" it, as apparently if you have numlock enabled (which I do on login) pressing "Enter" sends escape code: "^[[13;129u", but if you disable numlock it is typed in as per documentation: "0x0d - for the Enter key", which in any ascii table is Carriage Return.
And yes, issuing reset restored normal terminal operation.
Yes, in such a case, use the terminals native reset capabilities. And hopefully someday shells will learn how to interpret the full keyboard protocol, making it possible to type reset in any mode.
tedunangst|4 years ago
amadeusz|4 years ago
But not to trust what I just read I've installed kitty and tested it and you can type in the "reset" just fine. I hit a bit of a problem with "Entering" it, as apparently if you have numlock enabled (which I do on login) pressing "Enter" sends escape code: "^[[13;129u", but if you disable numlock it is typed in as per documentation: "0x0d - for the Enter key", which in any ascii table is Carriage Return.
And yes, issuing reset restored normal terminal operation.
aumerle|4 years ago