Oh, I didn't consider this because it's super obvious, and also the presumption of the whole thread (switching Fn/Ctrl) until you entered it. What's the value in pointing this out yet again?
>> you take small, generally inaccurate swipes at trivial stuff I write
> The swipes are also generaly accurate, thus you keep trying to do all the meta instead of addressing them directly.
Of course you write this in a post where you again only pull out very small things in my previous post, and engage with none of my larger points:
- It doesn't seem like any of your suggestions are possible
- even if they are with something like Karabiner, "My point is that it's always gonna be a little imperfect and maybe a lot of work"
>> Sorry then, what did you mean by "docs" here
> Company's keybinding help web page? You're making it up by trying to move the goalpost to narrower scope of "newer hardware" or "API docs"
No, all I'm saying is that going from "docs" to "API docs" on a site like HN isn't a big leap, and I was just making an off-hand remark that you've dug into multiple times now.
> 1. You can spend very little time with a few tweaks (like using a different keybind to cancel in the terminal).
You've not responded to my questions about specifics on this for either Terminal.app or iTerm2. I'm forced to conclude you don't actually know how to do this, if it's even possible. Also FWIW "using a different keybind to cancel" isn't something you've suggested before, which I know can be done in config files. You've only gestured vaguely at some context-dependent logic and rebinding Copy.
> 2. And no, it's not about consistency with other OS since the better design of Cmd on a Mac is NOT consistent with Windows. The goal is to achieve consistency WITHIN the OS so you can, for example, use the same key combo to copy in all apps
You can't really mean this. Are there macOS apps where Cmd-C isn't copy and adjusting the binds in System Preferences or Karabiner will fix it? I find that hard to believe.
