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

  • QuandaleDingle@lemmy.worldEnglish
    101·
    7 hours ago

    Just don’t buy an AI slop PC and get a Thinkpad, or a Framework laptop instead. Vote with your wallet. If you already own an AI PC, well, OP’s post might help.

    • fuckwit_mcbumcrumble@lemmy.dbzer0.comEnglish
      1·
      23 minutes ago

      Lmao. All non shit PCs are “ai PCs” now. It’s already built into the CPU. All you need is not 8 gigs of ram and to put that button and Microsoft hands you that sweet sweet dosh.

    • helpImTrappedOnline@lemmy.worldEnglish
      5·
      5 hours ago

      Pretty sure MS made this a “standard keyboard” button, which could mean it needs to be included for the OEM to be able to put windows on the machine.