Archives/input-remapper
2
0
Fork 0
mirror of https://github.com/sezanzeb/input-remapper synced 2024-11-08 07:10:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

wip

Browse Source
This commit is contained in:
sezanzeb 2020-11-17 21:09:28 +01:00
parent 7b47d8f18a
commit 9bf255c42b
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
HELP.md
View File

@ -1,5 +1,8 @@
# The problems with overwriting keys # The problems with overwriting keys
Branches for all that stuff exist to archive it instead of loosing it forever.
Look for branches called "fifth", "fourth", etc.
**Initial target** You write a symbols file based on your specified mapping, **Initial target** You write a symbols file based on your specified mapping,
and that's pretty much it. There were two mappings: The first one is in the and that's pretty much it. There were two mappings: The first one is in the
keycodes file and contains "<10> = 10", which is super redundant but needed keycodes file and contains "<10> = 10", which is super redundant but needed
@ -52,8 +55,7 @@ mouse buttons with a single symbol file. Key-mapper listens for key events
in /dev and then writes the mapped keycode into /dev. For example, if 10 in /dev and then writes the mapped keycode into /dev. For example, if 10
should be mapped to Shift_L, xkb configs would disable key 10 and key-mapper should be mapped to Shift_L, xkb configs would disable key 10 and key-mapper
would write 50 into /dev, which is Shift_L in xmodmaps output. This sounds would write 50 into /dev, which is Shift_L in xmodmaps output. This sounds
incredibly simple and makes me throw away tons of code. Branches for all that incredibly simple and makes me throw away tons of code.
stuff exist to archive it instead of loosing it forever.
# The various mappings # The various mappings