this post was submitted on 07 Feb 2026
339 points (98.6% liked)

Technology

80795 readers
3674 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

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.

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

you are viewing a single comment's thread
view the rest of the comments
[–] pupbiru@aussie.zone 1 points 3 hours ago* (last edited 3 hours ago) (2 children)

well that’s what they should have done but now what it’s implemented there are a lot more parties that need to come to the table to fix the mess… some hardware might not be able to fix the mess, but i’d be surprised if this shit show were implemented on hardware rather than firmware

[–] jjlinux@lemmy.zip 1 points 2 hours ago* (last edited 2 hours ago)

It has to me software/firmware based, right? Right!?

[–] SlurpingPus@lemmy.world 1 points 3 hours ago (1 children)

Eh, MS can just issue new requirements for their compatibility stamp, just like they did in the first place and many times previously. Newly produced laptop and keyboard models would have the fixed behavior, the same way they got the broken behavior.

[–] pupbiru@aussie.zone 1 points 3 hours ago* (last edited 3 hours ago)

new ones sure but there are a bunch of these broken machines out there now: far more than there otherwise would be, because microslop forced the upgrade for windows 11

i guesssss if they do it soon enough the existing models will still be in their support period and they’d kinda be forced to update, assume it’s a software or firmware fix