5 ms·

It's not a hard problem. The problem is that the less common use case is being given the nicer UX. I use copy and paste 100x more often than the interrupt codes

It's not a hard problem. The problem is that the less common use case is being given the nicer UX. I use copy and paste 100x more often than the interrupt codes produced by CTRL+V/C. Put those interrupts in the context menu instead of copy/paste. If the use case needs to be inverted, make it a user preference.

DuskStar 7y ago
Sometimes when I need ctrl+C, I really need ctrl+C right now. Being able to immediately cancel whatever stupidity I just typed is a very valuable thing.
- deckar01 7y ago
  > If the use case needs to be inverted, make it a user preference.
  - DuskStar 7y ago
    Fair enough. This might be a case of https://xkcd.com/1172/ https://xkcd.com/1172/
- OJFord 7y ago
  Which came first on Windows Clipboard UX is a bit of a mess on Linux, but notably on macOS copy is Cmd+C and SIGINT Ctrl+C, so this isn't an issue at all.
  - int_19h 7y ago
    The conflict long predates Windows. Ctrl+C to interrupt was inherited from TOPS (via DOS and CP/M). Ctrl+C to copy selected text was introduced on Xerox PARC, the granddaddy of all modern UIs. In DOS, some text-mode UI apps were already using it, although IBM CUA was more common.