this post was submitted on 07 Feb 2026
607 points (98.1% liked)

Technology

83449 readers
5086 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

(page 2) 50 comments
sorted by: hot top controversial new old
[–] probable_possum@leminal.space 6 points 1 month ago* (last edited 1 month ago) (1 children)

It's worth taking a look in the BIOS/ UEFI setup - maybe the key can be remapped there? Once the default F-key behaviour could be defined in there for ThinkPad devices.

[–] ageedizzle@piefed.ca 2 points 1 month ago (2 children)

That sounds way beyond the average users technical expertise. But it sounds like it might work. If you manage to figure out how to do that please let me know 

load more comments (2 replies)
[–] SlimePirate@lemmy.dbzer0.com 5 points 1 month ago

I remaped it to screenshot on hyprland

[–] RIotingPacifist@lemmy.world 5 points 1 month ago

Smells like antitrust violations.

[–] SUDO@reddthat.com 5 points 1 month ago

Didn't KDE say they were working on a way to remap it in a future update?

[–] TootSweet@lemmy.world 3 points 1 month ago

Jesus. I guess we're going to have to start figuring out how to reverse engineer our keyboards so we can install QMK on random built-in laptop keyboards and cheap Logitech membrane keyboards to repair the damage Microsoft has done to them.

[–] kamen@lemmy.world 3 points 1 month ago* (last edited 1 month ago)

I'm all for hardware remappable keyboards in laptops too - just like what you can have with an external one. I do realise though that this is a niche within a niche. From what I know only Framework (oh, and System76) is doing something like that.

[–] p0358@lemmy.blahaj.zone 3 points 1 month ago

My laptop had UEFI update that fixed the key-up thing and mentioned it allows holding the key in the changelog. So make sure to check for updates if you care

load more comments
view more: ‹ prev next ›