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

  • BorgDrone@feddit.nl
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    12
    ·
    2 days ago

    More like €4400 and it’s used heavily for 8+ hours a day as a development machine. It’s 4 years old by now (M1 Max, 64GB) and it still handles everything I can throw at it without breaking a sweat.

    Cheap laptops are nothing but trouble, in the end it’ll cost you more in replacements and lost productivity.

      • boonhet@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        19 hours ago

        To be fair that was also over a grand new. Not M1 Pro/Max territory but comparable to M1 Air new which outperforms it handily. But is also newer so it’s a moot point.

        They’re all great laptops, just at quite different price points.