3 ms·

Emacs does nothing when you press Ctrl-C. Try it. Then do it again. It isn't "copy"! And when was the last time you tried pressing Ctrl-C in vim? It's evident

Emacs does nothing when you press Ctrl-C. Try it. Then do it again. It isn't "copy"! And when was the last time you tried pressing Ctrl-C in vim? It's evidently been many years. Here, I'll save you a few keystrokes: vim /tmp/sigh ^C Type :qa! and press <Enter> to abandon all changes and exit Vim

amadeuspagel 4y ago
In fact this proves my point better. "How to exit vim?" wouldn't be such a meme question if people tried Ctrl-C.
- quesera 4y ago
  This proves only that people like to complain even if their complaints are uninformed. We knew that already. Vim added Ctrl-C messaging because people complained about remembering :q. Anyone complaining about that today is just drafting off the historic humor and making a show of their ongoing ignorance.
fnordpiglet 4y ago
And what does pico do? (Display cursor position) what about in control D? Terminate the input stream? Nope. It deletes the character under the cursor. Line oriented interactions ^C as break maybe makes sense. In a screen oriented termcap application I don’t think you are right.
- quesera 4y ago
  Pico owns zero mindshare in UNIX software. Ask yourself why. This is my point.
  - fnordpiglet 4y ago
    At one time it did. In fact I think exactly zero screen oriented editors I have ever used in a terminal don’t honor control c as break. Giving a statement that it doesn’t work isn’t handling it the way the terminal line oriented programs work.
    - quesera 4y ago
      I would not argue that a screen-oriented editor should interrupt/exit on Ctrl-C. Certainly not without confirmation. (Note that "Break" is another key sequence entirely. If someone asks you to send a Break, you would not send Ctrl-C.) I am arguing that setting Ctrl-C to any other action (esp a very common action like Copy) in a terminal environment application of any kind, e.g. a screen-oriented editor, is a bad idea.

amadeuspagel 4y ago

In fact this proves my point better. "How to exit vim?" wouldn't be such a meme question if people tried Ctrl-C.

quesera 4y ago
This proves only that people like to complain even if their complaints are uninformed. We knew that already. Vim added Ctrl-C messaging because people complained about remembering :q. Anyone complaining about that today is just drafting off the historic humor and making a show of their ongoing ignorance.

fnordpiglet 4y ago

And what does pico do? (Display cursor position) what about in control D? Terminate the input stream? Nope. It deletes the character under the cursor. Line oriented interactions ^C as break maybe makes sense. In a screen oriented termcap application I don’t think you are right.

quesera 4y ago
Pico owns zero mindshare in UNIX software. Ask yourself why. This is my point.
- fnordpiglet 4y ago
  At one time it did. In fact I think exactly zero screen oriented editors I have ever used in a terminal don’t honor control c as break. Giving a statement that it doesn’t work isn’t handling it the way the terminal line oriented programs work.
  - quesera 4y ago
    I would not argue that a screen-oriented editor should interrupt/exit on Ctrl-C. Certainly not without confirmation. (Note that "Break" is another key sequence entirely. If someone asks you to send a Break, you would not send Ctrl-C.) I am arguing that setting Ctrl-C to any other action (esp a very common action like Copy) in a terminal environment application of any kind, e.g. a screen-oriented editor, is a bad idea.