3 ms·
> Ctrl-C has meant "Interrupt" since the 1960s. Terminal != Terminal application Would you really want your SSH connection or editor session with unsaved chan
by alpaca128 4y ago
> Ctrl-C has meant "Interrupt" since the 1960s.
Terminal != Terminal application
Would you really want your SSH connection or editor session with unsaved changes just exit after pressing one key combination? Interactive applications have different requirements than a commandline with much more limited inputs.
There's no reason to be against Ctrl-C for copy in a text editor.
- quesera 4y agossh is a transport method. Of course it should not interpret in-line application commands. xterm should also not respond to an application command. An editor is an application, and it should respond. You can choose to handle interrupts instead of immediately exiting of course. But the meaning is intact. A well-behaved application in a POSIX environment will not fight the well-established conventions. There are many reasons for this, but the two most obvious are: - The implementation of the expected behavior might be outside of your control. Try pressing Ctrl-S in some terminals, and you will find that it does not reach the application because flow control is handled at a lower layer. By convention. - Just don't abuse your users! If they get accustomed to using the non-standard Ctrl-C for copy, and then use that same action in another application, they might lose data and it will be your fault.
- amadeuspagel 4y ago> If they get accustomed to using the non-standard Ctrl-C for copy, and then use that same action in another application, they might lose data and it will be your fault. That ship has sailed. Today, most people are accustomed to using Ctrl-C to copy.
- quesera 4y ago> Today, most people are accustomed to using Ctrl-C to copy. That is not true, in the relevant context: that within which this software is released.