Remap of Windows key #512
Replies: 2 comments 1 reply
-
I can add that i found a file in ~/.config/input-remapper/xmodmap.json which contained all code mappings. It missed one entry for keycode 206 so I added one line with Super_L and keycode 206. But when i started input-remapper then it changed it right back. |
Beta Was this translation helpful? Give feedback.
-
I noticed that the keycodes printed when using "input-remapper-gtk" and "xev -event keyboard" are NOT identical. Thus, when I hit the windows key i get a keycode 125 (Multikey) in input-remapper-gtk, whereas I get a keycode 133 from xev. When i use "xmodmap ~/.Xmodmap" to do a manual remapping, then I get the right result so I can use Gnome keyboard shortcuts with the Windos key as intended.
in order to make it work I had to remove mod4 mapping which had already grabbed the Super_L :
Maybe the problem is caused by the Super_L is already grabbed by some earlier key mapping somewhere. So is there a method in input-remapper to first remove the default mapping of Super_L, and then re-assign it to Multikey ? It is strange why "input-remapper-gtk" and "xev -event keyboard" gives different values for the keykodes of the windows key - and different values for the mapping to Super_L for the two methods ? Is there anyone who can explain this ? |
Beta Was this translation helpful? Give feedback.
-
I use Ubuntu 22.04 with the lates .deb file from here, and tried to do a remapping af the windows key (Multikey) to Super_L. However Super_L is not part of the keys in the pulldown menu that can be mapped to it seems, but Super_R is there however. What i want is to map Multi_key (Windows Key) to Super_L - i.e. from keycode 133 to 206 (seen from "xev -event keyboard" command). But it seems it is not possible. Maybe I missed something ? Help would be appreciated. The result is the same in Ubuntu Xorg and Wayland.
Beta Was this translation helpful? Give feedback.
All reactions