Remapping Copilot Key on Laptop

[winkelnp]

I recently bought a new laptop and (ofc) immediately nuked the windows on it. As all the new windows laptops now replace the right control key with a copilot key (Super Shift F23), I would like to rebind that back to right control.

A complicating factor was that F23 apparently isn't in the standard keymap anymore so dmesg was giving me something along the lines of "key not recognised pls give it a keycode with setkeycodes 6e <keycode>"
I did this, checked to see that I wasn't overwriting anything and gave it the keycode 97, which is the keycode after F12 that is empty in the standard keymap.

I then set the keybind in hyprland.conf with bind = $mainMod SHIFT, code:97, exec wtype -k Control_R thinking that would just send right control in place of that whole combo.
Instead what it's doing is sending SUPER SHIFT R_CTRL for some reason.

Does anyone have any clue what I could do?

[Aqa-Ib]

Try https://github.com/rvaiya/keyd

[winkelnp]

Thanks for the speedy reply! I can't see a way of using a keycode, they seem to use names for all the keys in the examples, do you know what I could do there?

[Aqa-Ib]

Right, if I were in your situation I would open an issue at keyd, the developer is helpful.

[Aqa-Ib]

Look rvaiya/keyd#825

[winkelnp]

Thanks, I've sent in an issue about the keycodes thing, I'll try that solution in the mean time :)

[Aqa-Ib]

Could this work though? bind = $mainMod SHIFT, code:97, exec wtype -m shift -m super -k Control_R

[winkelnp]

using -m to release the modifier status doesn't seem to be doing anything, while using -p to just release the key aborts the whole thing

I think what must be happening is that releasing the modifier in wtype is being overridden by the fact that the system sees that the key is still pressed and is adding the status right back. This would explain why there are so many modifier events happening in wev?

[Aqa-Ib]

Try:
bind = $mainMod SHIFT, code:97, exec wtype -M Control_R

[winkelnp]

It errors saying that Control_R isn't a valid modifier

[winkelnp]

Is it maybe an issue that the system sees the modifier win as Mod4? or would that be irrelevant and translated by wtype?

edit: nope not the issue, works fine on other things.
Interestingly: if I rebind e.g. F12 to wtype -M win -k r -m win it doesn't show up in wev (like other keybindings in hypr), but it also doesn't show my run launcher

[Aqa-Ib]

using -m to release the modifier status doesn't seem to be doing anything, while using -p to just release the key aborts the whole thing

I think what must be happening is that releasing the modifier in wtype is being overridden by the fact that the system sees that the key is still pressed and is adding the status right back. This would explain why there are so many modifier events happening in wev?

Yes I am also testing it and I think that this is the case.

[Aqa-Ib]

There is a person in reddit who achieved this using evsieve: https://www.reddit.com/r/linuxquestions/comments/1dnh6ge/comment/lhkoy5h/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

[winkelnp]

That works a like a charm :)
not sure how I feel relying on an aur package to be running all the time my system is active though...

[Aqa-Ib]

you can download the pkgbuild and manage it yourself

[Aqa-Ib]

glad it worked though, enjoy!

[winkelnp]

Thank you so much :))

[Aqa-Ib]

you are welcome, have a nice one!