| ▲ | jack_pp 3 days ago |
| Heh, shortcut muscle memory is the reason I returned my Mac mini one week after trying it. I sure am not gonna remap my brain for apple after 20 years of Linux and windows. |
|
| ▲ | nsagent 2 days ago | parent | next [-] |
| Maybe you mean it's too much effort, because I'm sure you could. I was taught touch typing on a QWERTY keyboard in the summer between 6th and 7th grade. Last year I switched to Colemak after nearly 30 years of QWERTY. |
| |
| ▲ | jack_pp 2 days ago | parent [-] | | Oh I have no doubt that I could but I don't see why since linux already does what I need and I don't see any compelling reason to switch. I was just curious to see what all the hype was about with the new m1 CPUs and give it a shot. |
|
|
| ▲ | computably 3 days ago | parent | prev [-] |
| It's easy and reasonably quick to set up key remapping (via Karabiner). |
| |
| ▲ | taftster 3 days ago | parent [-] | | Yes, but specifically in the context of Terminals (as discussed in the original article), it's really convenient to be able send Ctrl-C (break) differently than Cmd-C (copy). So yes keyboard remapping is an option. But there's just differences you can't remap because of the extra meta keys on Mac (and I guess on Windows too, with the Copilot or Start keys in play). | | |
| ▲ | inejge 3 days ago | parent [-] | | > it's really convenient to be able send Ctrl-C (break) differently than Cmd-C (copy) Right, and even on Linux you can do it by using the four-fifths forgotten CUA shortcut Ctrl-Insert for copy (and Shift-Insert for paste.) Although I'll admit to using Ctrl-Shift-C/V most of the time. | | |
|
|
