618
The new Microsoft copilot key is impossible to properly remap. (discuss.tchncs.de)
submitted 9 months ago by to c/technology@lemmy.world
151 comments fedilink hide all child comments
 

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

dell laptop with copilot key highlighted
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 9 months ago* (last edited 9 months ago) (1 child)

given the complexity of doing in hardware, and the simplicity of doing it software, you’d hope yes (in which case perhaps there will be firmware hacks) but you can never truly account for the stupidity of hardware companies

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •