Ctrl+C is a method of generating a standard ASCII character which has meant "ETX" (end of text, sometimes "interrupt") for many decades.
Other control chars are useful too. In addition to C, I use S, Q, D, Z, V, O, N, I, G, H, M, L, J, Y, A, E, K, W ... probably others ... fairly regularly.
So in the early 1980s, along comes MacOS which needs keyboard shortcuts for GUI actions. What does Apple do? They add a key to the keyboard, an Alt or Meta equivalent called "Command". OK, awesome.
Then Windows comes along. Microsoft says "eh, who cares let's break it all", (or more charitably "we don't control the hardware and can't add a key, so let's break it all") and reuses Ctrl+C for copy. Et cetera.
Then Linux desktop environments come along and say "well people really like Windows...we don't, but most people who might try our DE probably do, so let's borrow the bad ideas from Windows instead of the good ideas from Unix or MacOS. Let's use Ctrl+C for copy! But also the command line is kind of important on Linux, so let's screw everything up and use Ctrl+Shift+C for copy in the terminal only because who cares about usability and UX consistency? Not us!"
That was 25 years ago. Nothing has improved since then. Alas.
Apple added three keys on the original Mac keyboard. The Command key, the Option key (which is used, more or less, as a second Shift key) and the Enter key (not to be confused with Return). The Enter key eventually was deprecated and made equivalent to keypad-Enter. It's now mapped to Shift-Return on Macs. The Option key, not the Command key, is now mapped on modern keyboards to Alt. The Command key is its own wonderful beast. Both ESC and Control were missing; both were added back later.
I recall reading somewhere that Jobs hated Open Apple and Closed Apple. But thank goodness for ⌘ !
Wikipedia has both the //e and the Lisa with a release date of January 1983. But of course the Lisa project goes way back!
I should have been more clear, indeed, I find sending signals to the system using the `ctrl` good and proper. I have no problem with the control key, sequences, or characters. My issue is ignoring the sheer, maddening, brilliance of the command key...
> Then Linux desktop environments come along and say "well people really like Windows...we don't, but most people who might try our DE probably do, so let's borrow the bad ideas from Windows instead of the good ideas from Unix or MacOS. Let's use Ctrl+C for copy! But also the command line is kind of important on Linux, so let's screw everything up and use Ctrl+Shift+C for copy in the terminal only because who cares about usability and UX consistency? Not us!"
Yes :jacknicholsonnoddingandsmiling:
Linux and non-mac *nix systems emphasize how powerful the command line is but totally fucking ignore even the most fundamental of modern use case(s): copying and fucking pasting. It's just fucking silly. Yew (being a fancy terminal box thing) ain't that powerful if yew cain't (yeah, that's can't + ain't) copy and paste some shit. It's like someone bragging about how fast they can type with their feet, "...cool brometheus... how about you get a fucking job and pay rent for once?"
shakes fist menacingly at the ether
But they do control it enough to add the Windows logo key and the context menu key.
I use the Windows logo "Super" key a lot (mostly for workspaces) and I miss the context menu key which is there on my office keyboard but lacks on my laptop (which even has a keypad). Being able to open a context menu without using a mouse is a very useful convenience.
But I agree it was a good thing to have.
It wasn't Microsoft though. Common GUI hotkeys like Ctrl+Z/X/C/V/P were introduced in Xerox Alto first, and everybody else used this as a convention, including Microsoft.
I'm not sure what hotkeys Alto Executive used, and whether there was a mnemonic conflict at all.
Obviously either of these would rarely happen, but every time I use a terminal in macOS I end up accidentally killing a process because I can't keep the modifier keys straight, so I'm sensitive to introducing the issue on Linux. (On Linux, I have the opposite problem, which is that I try to Ctrl-shift-c in Firefox, which opens the dev tools.)
I don’t see how that can happen. If you tap c twice, you either copy twice (copying keeps text selected), which is harmless, or, if you release the control key between the taps, type a c, which doesn’t kill the process.
The accidental deselect, on the other hand, can indeed be problematic.
And then just middle click to paste again.
Also eOS implementation has its issues, smart copy needs to be disabled too for Kinto to work - thankfully it’s practically the only one.
The one time I get really frustrated with conflicting keyboard shortcuts is when trying to do terminal work in a web browser, through, like the odd KVM session when SSH is down. The number of times I instinctively pressed Ctrl+W to correct a word in bash and instead close the whole session... Or, depending on emulator, inability to paste. Even more frustrating that these situations are commonly high-pressure.
Same with the Windows home/end for sending the cursor to the beginning/end of line. That entire block of keys is only useful for navigating documents, they’re just unergonomic to use when you’re also typing.
For home/end:
Ctrl+A/Ctrl+E for all shells, ^/$ otherwise
You will need SharpKeys[2] and Autohotkey[3] at least in my set up.
[1]: https://images-na.ssl-images-amazon.com/images/I/61oeDlRN4QL...
I bought one, threw it into garbage the second day.
Just checked and you can even order from Amazon JP and let ship to Europe. Nice, problem seems to be solved. Did you ever order something from them?
Do you know what scan codes (or in general what characters) those Japanese keys next to the spacebar send when the keyboard layout is set to US?
All you do is press the key in the "Type Key" blank in SharpKeys.
I have actually gotten a Japanese Thinkpad keyboard for my laptop although its for the T420 model. I would have to check my Desktop to see how this works again(on a laptop right now) if you want the actual scan codes. I will say I haven't gotten this to work on Linux just Mac and Windows unfortunately.
(1) Where did you get the (internal) JP keyboard for your Thinkpad, Ebay or Lenovo parts sales?
(2) Imagine those 5 keys on your JP keyboard...
_ _ _____ _ _
|1||2||Space||4||5|
...how convenient is it for your left thumb to hit 1 and 2 and for your right thumb to hit 3 (Space), 4 and 5, each on a scale from 0 to 10? Bonus question: do you have small, medium or big hands?And how did you get the idea to use a JP keyboard?
ps I use AHK, have to check out Sharpkeys!
2) I have 2 of the 3 Japanese keys mapped to control/modifier and and the third mapped to space. Your picture seems to be off there aren't four modifier keys but three. The switch is quit seamless between a Mac and Windows. Medium Hands. I was analyzing keyboard layouts.
How was your experience, would you use them again? And I assume you did a full managed buy?!
If this thread is getting restricted you can also PM me on reddit with the same username.
Probably this will not work for many people but is great for me since I have tons of keyboards shortcuts in my IDE and DE that use ctrl and shift . I think I use Alt only for Alt+tab but I don't need it that often because I have 7 virtual desktops that I reach using Ctrl+f1/f7
(And Linux the OS doesn't have any opinion on GUI terminal keybindings. You may be tempted to point your finger of blame towards X11 next, but X11 traditionally the text selection is mouse based with implicit copy on select - paste defaults to shift-insert in the bundled X11 terminal emulator. The shift-ctrl-c charade was created by gnome-terminal I think)
so alt+c for copy, alt+v for paste etc. it solves the terminal problem AND it reduces strain on the thumb.
Ctrl + Shift + Ins (paste) and Ctrl + Shift + Supr (copy)
Ctrl + Shift + v (paste) and Ctrl + Shift + c (copy)
Most terminals today have a copy-on-select feature, which means you don't need to ctrl-c at all. Just select and ctrl-v.
The Windows GUI copied the Mac’s keyboard shortcuts (originally from Lisa?) but didn't have a dedicated key for them so re-used the existing Ctrl key, which already had a meaning on text-based operating systems. (This happened because Microsoft had no input into hardware keyboard layouts, and wanted to make software compatible with the plethora of IBM-Model-M-layout keyboards available in 1985–1990.)
Then Linux GUIs wholesale copied every feature of Windows they could including the keyboard shortcuts, in a context where this was even worse, because now existing Ctrl-based shortcuts from terminal software were directly in conflict with new Ctrl-based shortcuts from Windows.
Except for that particular action (select some text on terminal then copy) you have to use mouse to do the "select" part anyways.
Where a mouse is really needed is in action games. A touchpad is too slow there.
In this context there is a lot of difference between a mouse and a touchpad. For example, I select text with the keyboard most of the times in emacs and in any other input box (not in vim, is it even possible?). So I'd lose time by reaching to a mouse. I hardly have to move my hands to use my touchpad.
The thing is it's the default on iTerm2 on the Mac, so every time I set it up I spend a week thinking "why is my clipboard always completely full of shite" before I remember and turn it off.
(YMMV, you may like this, you may actually have proper clipboard management, and so on. I didn't say this was a logically consistent rant.)
X11 by contrast has by default 2 buffers so you never clobber your buffer filled by control+c however some clipboard management software optionally syncs the 2 buffers bringing back the behavior you dislike.
It's possible that this isn't enabled by default, but I'm virtually certain it is because it catches me out every time.
Personally I find this method much more usable than the traditional windows-style clipboard.
Either way, you want to generally avoid C-c for copy in terminals because it's already bound to the all important "send sigterm signal to foreground process". This is on a long list of ancient cruft that exists in terminal emulators and shells.
I am serious about not wanting users of Kinto to feel like they are dying a death of a thousand paper cuts because they have to stop what they are doing and add yet another keymapping. Kinto can't get every app remapped right 100% of the time - but it gets awfully close still.
Initially I did not write Kinto that way because I didn't think it to be all that possible and with setxkbmap it was very difficult to understand and properly implement such a configuration. Probonopd, who does write some wonderful articles about UX related topics that I've also seen hit the frontpage here mentioned not wanting to remap terminals at all - I agreed and eventually delivered. He also made sure that I worked out wordwise hotkeys as well.
Also with it being rewritten, several months ago, to use xkeysnail it is also very simple to add additional hotkey remappings to as well.
Absolutely. But it's not cruft. It's the original meaning of the character, and the standard method of generation.
Ctrl+C is just like any other keypress which maps to a standard ASCII representation.
The error is in reusing ASCII chars for GUI actions. This was an obviously-bad idea in 1985, and it has never become a better idea.
My perspective is that control characters were a bad idea from the beginning. Then again, so are ubiquitous predefined keyboard shortcuts like C-c.
Having user interaction predefined makes it more difficult to change keyboard layouts and shapes.
So if you have in-band signalling, you need a method to generate those signals. I don't think there was any other viable way to solve this problem, and honestly it has worked almost flawlessly.
Of course Microsoft is a big exception, but that could hardly have been predicted 20 years earlier.
My point here is that we are so steeped into tradition that usability suffers.
In-band signalling is inherently a bit of an architectural challenge. But the problem is solved. The entire internet is run on in-band signalling! We're going on 35 years for TCP/IP, and more like 50 for ASCII control chars. They work very, very well.
Yes, Microsoft broke control character generation for users of their OS, but that's a compartmentalized failure, and easily avoided. The Ctrl+Shift GUI workaround in Windows (and copied in Linux) is not elegant. But any alternative without control chars would be a total loss of functionality.
Ctrl+C being broken by Copy is a trivial example. There's a whole alphabet of control chars (in fact there are 32), and we all use more of them than most people realize[0]. Some have dedicated keys on the keyboard (backspace, return), but obviously not all of them.
I use about a dozen control characters regularly. This is not unusual for someone who works closely with server operating systems.
[0] I'm not sure how to gauge your knowledge of communication signalling or protocols, so I apologize if I'm being pedantic. It sounds like you have ideas about alternatives (and this is interesting to me), so I am curious about any specifics you can share or link to.
stty intr ^X
Then ctrl-c will no longer bother you, and your muscle memory will quickly adapt as X is very close to C
By the way, I don't even know if I could paste with control c or control shift c back then. Maybe there was only middle click.
I could try again now and see what happens.
'cuz it turns out, I personally hate how Windows and Linux do things with `ctrl`. Coming from a Mac, my biggest and most consistent annoyance is that the `ctrl` key is fucking useless at best...
One of the most common use cases for the `ctrl` key is COPYING shit and followed by PASTING shit and it DOES NOT WORK in a fucking TERMINAL... Because `ctrl-c` sends an interrupt, I don't know what `ctrl-v` sends and I don't give a shit as long as it is not pasting my fucking buffer.
Seriously... on Linux this has got to be the worst default ever made. Sure `ctrl+shift-c` will copy things but it's fighting decades of fucking muscle memory... and if I miss the shift, "boom" repl killed. Great experience for someone totally new to the OS, just follow this tutorial, start by copying this from your spooky new black box: "[^C program exited." I'm willing to bet I ran into that exact thing years ago in highschool and just attributed it to me being a dumbass and gave up: "damn, I can't even copy paste shit in this, I'll never figure it out" instead of that being the worst most absurd default on a *nix system ever.
And the "Windows/Hyper" key? Ah yes, here's a key that was created to globally disrupt whatever you are doing. So where is the obvious location? In-between two keys that are ONLY used as modifiers; so, when you accidentally hit the wrong one you always lose focus. Even better is when you accidentally do so on both characters; enabling some obscure setting or window you can't correctly undo because you don't know what you pressed!
I'm glad to know there are at least some other sane people out there who have realized 1992 may not have been the pinnacle of desktop computing...