This is why I love my macOS keybindings. I can not believe what a waste the Windows key is compare to the Command. I use extensive AutoHotKey scripts and hardware keyboard macros to compensate.

I mostly SSH to Linux, but when I use a Linux Desktop, I struggle to get the key bindings to my taste.

Check out kinto.sh, which does this for you:

https://github.com/rbreaves/kinto

The Windows key is a tragic misstep in computer evolution. It should not exist.

The "Windows key" is just Microsoft branding. It was called the Super key before that, and it dates back to the 1970s.

Here's an example on a Sun keyboard, labelled with a diamond: http://xahlee.info/kbd/iold51593/Sun_Microsystems_Type_6_Key...

> I also wish we'd have stuck to a clearer separation of which modifier keys apply to the OS/desktop level, which ones are app level, and which ones are text/input level.

Oh, absolutely.

A small mercy is that software on Linux never seems to use the Windows aka super key in shortcuts. So i set up my desktop environment such that all its shortcuts use super. It means i have a completely nonstandard setup, but at least it means there are no collisions!

Apps mostly steer clear of ctrl + alt + funky key combinations (ie not letters), so you can have those for locking, rebooting, etc.

But it would be lovely if this was systematic, codified, and standardised.

Try kinto:

https://github.com/rbreaves/kinto

> I wish this had caught on.

It did. It's still available in Windows 10.

And it's what everyone used throughout the eighties and most of the nineties, until Microsoft copied the silly Cmd-X/C/V (only with Ctrl in stead of Cmd) from Apple for Windows 95 or thereabouts.

Note that these work as advertised on Windows 10 at least. I seem to recall those were listed as edit keys in a cmd or terminal window at some time in the past, but not when I just checked.