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
[–] -3 points 9 months ago

Performance is good, but not great, and, again, is trounced by most of its equivalents, even the Surface Book.

Sure, you can find an equivalent priced laptop that will beat the MBPro at one metric, but it’ll fall short on others. It’s faster but it has a cheap case , crappy trackpad, shit screen or terrible battery life, etc.

There are very few laptops out there that are as good in every metric as a MBPro. It is simply the best total package.

  • permalink
  • fedilink
  • source
  • parent