this post was submitted on 07 Feb 2026
391 points (98.0% liked)

Technology

80795 readers
3580 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
[–] attero@discuss.tchncs.de 33 points 18 hours ago (2 children)

nope, the hardware / keyboard controller sends a complete key sequence instead of a distinguishable key-up and key-down event. The OS can interpret that sequence as it sees fit, but you loose the physical key-up signal when you release the key with your finger.

[–] JohnEdwa@sopuli.xyz 2 points 9 hours ago

Though any competent manufacturer, especially when talking about laptops, would still have the application key under FN (as is shown in that example image), and give the ability for users to select which one is the default function in the BIOS.

[–] Corngood@lemmy.ml 13 points 14 hours ago (1 children)

That's insane. Even if they did this intentionally to be as difficult as possible, they locked themselves out of being able to detect long presses?

[–] attero@discuss.tchncs.de 10 points 14 hours ago* (last edited 14 hours ago)

I've made an update edit: Some hardware vendors fucked up when to send the key-up-sequence apparently so now every keyboard can behave differently. I don't know if this makes the situation better or worse.