Since I type with the "Dvorak" keyboard layout, the shortcuts such as ctrl-c, ctrl-x, or ctrl-v are not comfortable anymore for the left hand. And even one of them require two hands to press.

Furthermore, applications such as Intellij have their shortcuts, which I'm used to. So for these shortcuts I prefer "Querty". Since there is no way to configure this, it is necessary to intercept the keys and remap the keys from "Dvorak" to "Querty" when pressing CTRL, ALT, WIN or any of those combinations.

With X.org I was relying on the wonderful project from Kenton Varda. And then came Wayland.

XGrabKey() works partially with some application but not with others (e.g., gedit is not working). Since XGrabKey() is an X.org function with some support in Wayland, I was looking for a more stable solution. After a quick look to this repo, I saw that Kenton added a systemtap script to implement the mapping. It scared me a bit to follow that path, so I implemented an other solution based on /dev/uinput. The idea is to read /dev/input, grab keys with EVIOCGRAB, create a virtual device that can emit the keys and pass the keys from /dev/input to /dev/uinput. If CTRL/ALT/WIN is pressed it will map the keys back to "Qwerty".

Kenton Varda reported that this project also works with Chrome OS if started as root.

The mapping does not work with Eclipse. Regular typing uses Dvorak, while the shortcuts are using Qwerty (I have not figured out why). This results in a situation where a Qwerty key gets remapped according to the Dvorak mapping.

• create binary with make
• install it with sudo make install

This will copy 3 files: dvorak, 80-dvorak.rules, and [email protected]

The file is triggered on the udev rule and call dvorak systemd service with the device that was attached. The rule contains the search term "keyb", that will match case insensitive the device name. Only a device with name that contains the substring "keyb" will be considered. To prevent an endless loop, the newly created virtual device is excluded from mapping itself.

That way, dvorak will be called whenever an input device is attached.

From here, ensure that your first keyboard layout is set to Qwerty and your second layout is Dvorak.

If you see the above message in syslog or journalctl, it means that your keyboard device name does not have the string "keyb" (case insensitive) in it. For example, Not a matching device: [Logitech K360]. In order to make it work with your device, in [email protected], you can call be the executable with

ExecStart=/usr/bin/dvorak /dev/input/%i keyb k360

I used the following sites for inspiration:

• https://www.kernel.org/doc/html/v4.12/input/uinput.html
• https://www.linuxquestions.org/questions/programming-9/uinput-any-complete-example-4175524044/
• https://stackoverflow.com/questions/20943322/accessing-keys-from-linux-input-device
• https://gist.github.com/toinsson/7e9fdd3c908b3c3d3cd635321d19d44d