The new Micro~~soft~~slop 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.
- Linux workaround: https://github.com/m-bartlett/remap-copilot?tab=readme-ov-file
- Windows workaround https://github.com/randyrants/sharpkeys/issues/560
- https://xcancel.com/dcolascione/status/2019936377408811319
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
Can confirm. Decided to pop for a base MBA, but with 32g ram, about a year ago, and it’s fantastic. Unbelievable battery efficiency, completely silent (passively cooled), and still decently performant for when I want to compile something/do a cpu intensive thing. I’ve used MBPs as corp-issue dev machines for nearly a decade and a half now, so I’m quite comfortable in the ecosystem.
I still have my old T14g2 running fedora, though (in addition to a plethora of non-mobile systems). Also snagged one of those silly-cheap Acer laptops with a fairly late model i3 in it, because it was $200 and had a SODIMM and m.2 slot, just as a spare/extra (it’s running kinoite)