3 ms·
That's the point. That behavior is contrary to the expectation. Ctrl+C should not display a message: Ctrl+C should quit immediately.
by theandrewbailey 9y ago
That's the point. That behavior is contrary to the expectation. Ctrl+C should not display a message: Ctrl+C should quit immediately.
- bryanlarsen 9y agoOn many editors ctrl-c is the copy key. Not a good key to exit on...
- kpil 9y agoIt's the other way around - mapping copy to ctrl-c was a bit stupid...
- slrz 9y agoYep. Apple got this one right with the Cmd key. Much saner than the context-dependent hijacking of the control key with its long-established conventional usage.
- bryanlarsen 9y agoVery true, but that argument was lost over 20 years ago.
- chrisweekly 9y agoCTL-C, or CMD-C?
- brewdad 9y agoComing from the Windows world, I am happy that Ctrl+C doesn't make assumptions and quit. Imagine attempting to copy something and having your file close without warning.
- ygra 9y agoYou can intercept Ctrl+C on Windows just as well and do nothing, or something different than quitting.
- falcolas 9y agoHere's the problem: Ctrl-C isn't quit. It's keyboard interrupt, and that does not necessarily mean "quit".
- JdeBP 9y agoIronically, in vim, where the terminal is in non-canonical input mode when vim is in the foreground, it is not keyboard interrupt. (Nor is it in most modern shells, which also use non-canonical input mode in their command line editing mechanisms.)
- smoe 9y agoHow many interactive programs actually close immediately if you hit CTRL+C? Why would you expect that of vim? If nano were the editor you end up in, you would have the same problem.