4 ms·
That's what the reset button on old computers was for. In all seriousness can't you just Ctrl+C or Ctrl+Z and kill the process instead? Maybe there's something
by dudus 7y ago
That's what the reset button on old computers was for.
In all seriousness can't you just Ctrl+C or Ctrl+Z and kill the process instead? Maybe there's something that prevents this that I don't remember, my shell game is rusty.
- cjbprime 7y agoThey're sent to the telnet target, so that you can do those things on the remote machine.
- syntheticnature 7y agoNo, you can't, because telnet occupied the position SSH now does of remote connection to a shell on another machine. Your Ctrl+Z or Ctrl+C gets passed right through to control that remote machine, assuming you have a proper telnet server on the other side that negotiated the appropriate options.
- notananthem 7y agojust kill your telnet session on the remote machine?
- smush 7y agoReminds me of being a first time user trying to get out of VIM while following a tutorial. How frustrating it was then! If you have flailed around and messed with a file because when you type, it ignores your input until you use the 'i' character, suddenly you need to stop, close and reopen the file (because you don't know to hold the u key to undo). So, you do what works on DOS or nano, and hit Ctrl + C. Someone coded it such that if you hit Ctrl + C to exit, instead of exiting out of VIM immediately, the editor writes a message that says "to exit vim, you must type :quit". So you type that, and VIM responds with 'you have unsaved changes, please add ! to overwrite', so you type ! and it does nothing. After several seconds of confusion, you google how to get out of vim and the internet reveals the magic keystrokes ":q!" to finally get out of this dad blame file and get back to what you were doing. All of that (probably, in my cynical mind) to avoid following the principle of least surprise and have Ctrl + C = close, discard changes.