The new Microsoftslop copilot key always sends the following key-sequence when pressed:

copilot key down: left-shift-down left-meta-down f23-down f23-up left-meta-up left-shift-up
copilot key up: <null>

This means there’s no real key-up event when you release the key --> it can’t be used (properly) as a modifier like ctrl or alt.

The workaround is to send a pretend key-up event after a time delay, but then you mustn’t be too slow / fast when pressing a shortcut.

tldr: AI took a perfectly working modifier key from you.

— edit —
Some keyboards apparently do the “right” thing and don’t send the whole sequence at once, you can remap those properly with keyd, see: https://github.com/rvaiya/keyd/issues/1025#issuecomment-2971556563 / https://github.com/rvaiya/keyd/issues/825

copilot key down: left-shift-down left-meta-down f23-down
copilot key up: f23-up left-meta-up left-shift-up

this will still break left-shift + remapped copilot and left-meta + remapped copilot, but RCtrl remaps should work as expected

  • Mic_Check_One_Two@reddthat.comEnglish
    2·
    3 hours ago

    Yeah, my complaints about Apple all stem from the fact that my industry has a standard program that only runs on Macs… And every Mac I’ve used has inevitably ended up taking 4x as long to do basically anything else when compared to Windows or Linux. The only reason I ever use a Mac is because my job requires it, and even then it is only begrudgingly; if there was a way to run the program on anything else, I would have done so a long time ago.

    And yeah, I agree 100% about the “different first, better second” design choices. Lots of the most frustrating things about Macs are due to intentional design choices that Apple makes. Not because it is better for the user, but simply because it is different.