Hacker News Reader

Approximately 0% of terminal programs use control-c as copy. Conventions depend on context.

"Control-C sends SIGINT" has been a standard for longer than "Control-C means copy".

I'm well aware of that and the historical reasons that it's the case. I'm just using it as an example of breaking well established patterns that screw new users.

^C as copy is an example of breaking well established patterns that screw new users. Its THE canonical example in fact.

^C is SIGINT. ⌘C is copy.

I blame Microsoft.

Didn't Ms"S use to use CTRL-Ins or similar?

The name that you want to look up is Common User Access.

Well TIL, thanks! Interesting to know the history.

(I still have a few Windows apps we use at work that use these standards; good to know they actually were a standard.)

I really don't care who is responsible or which came first. I'm only pointing out the inconsistency and the problems it causes.

Don't worry, in few years new bindings will be familiar to new people straight from their birth date. Then they will complain about changes and you'll tell them that changes were made long before.

Shortly after the introduction of the first generation of brain-computer interfaces: "Why do I have to think of Ctrl-C to copy text in this program? All the other programs have me think of a banana to copy a selection!"

Reply on news.ycombinator.com