Archives
/
input-remapper
mirror of https://github.com/sezanzeb/input-remapper
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
uniq
reader-service-run-asyncio-fix
fix-ci
kljadsflka
placeholder
typealias-3.9-compatibility
beta
2.0.0-rc_mypy
v1
628-gui-suggestion
debounce-editor-2
log-input-events
toggle-macro-hold-timeout
xkb
led_test_merge
ifeq-and-returning
meta
flatpak
first
0.1.0
0.2.0
0.3.0
0.3.1
0.4.0
0.4.1
0.5.0
0.6.0
0.6.1
0.7.0
0.7.1
0.8.0
0.8.1
1.0.0
1.1.0
1.2.0
1.2.1
1.2.2
1.3.0
1.4.0
1.4.1
1.4.2
1.5.0
1.5.1
2.0.0
2.0.0-rc
2.0.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'efce80a911'
${ noResults }
input-remapper/PATHS.md

1.1 KiB
Raw Blame History

Folder Structure of Key Mapper

Stuff has to be placed in /usr/share/X11/xkb to my knowledge.

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>

This is how a single preset is stored.

Defaults

  • /usr/share/X11/xkb/symbols/key-mapper/<user>/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.