Archives/input-remapper
2
0
Fork 0
mirror of https://github.com/sezanzeb/input-remapper synced 2024-11-04 12:00:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
0c7f211475
input-remapper/PATHS.md
sezanzeb 22f4a832e4 update PATHS.md
2020-11-10 23:20:22 +01:00

1.4 KiB
Raw Blame History

Folder Structure of Key Mapper

Stuff has to be placed in /usr/share/X11/xkb to my knowledge. In order to be able to make backups of the configs, which would be expected in the users home directory, this is symlinked to home where the actual files are.

Every user gets a path within that /usr/... directory which is very unconventional, but it works. This way the presets of multiple users don't clash.

Presets

  • /usr/share/X11/xkb/symbols/key-mapper/<user>/<device>/<preset>
  • /home/<user>/.config/key-mapper/<device>/<preset>

This is how a single preset is stored. The path in /usr is a symlink, the files are actually in home.

Defaults

  • /usr/share/X11/xkb/symbols/key-mapper/<user>/default
  • /home/<user>/.config/key-mapper/default

This is where key-mapper stores the defaults. They are generated from the parsed output of xmodmap and used to keep the unmapped keys at their system defaults.

Keycodes

  • /usr/share/X11/xkb/keycodes/key-mapper

Because the concept of "reasonable symbolic names" (www.x.org) doesn't apply when mouse buttons are all over the place, an identity mapping to make generating "symbols" files easier/possible exists. A keycode of 10 will be known as "<10>" in symbols configs. This has the added benefit that keycodes reported by xev can be identified in the symbols file.