thurstylark
/
tlwiki
1
0
Fork 0
Code Issues 6 Pull Requests Projects Releases Wiki Activity

Small spelling mistake

This commit is contained in:
David Thurstenson 2017-06-05 17:09:52 -05:00
parent 12df5d98b1
commit 3d1aaa3dd4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Keyboard Mapping.wiki
View File

@ -43,7 +43,7 @@ A few notes on the format of this file:
* The format for the device identifying line for usb devices is `evdev:input:b0003v<Vendor ID>p<ProductID>*`. * The format for the device identifying line for usb devices is `evdev:input:b0003v<Vendor ID>p<ProductID>*`.
* If `<Product ID>` and `<Vendor ID>` contain letters, they must be capitalized * If `<Product ID>` and `<Vendor ID>` contain letters, they must be capitalized
* These scancodes can be quite device-specific, so it is wise to be specific to *at least* the vendor and product IDs * These scancodes can be quite device-specific, so it is wise to be specific to *at least* the vendor and product IDs
* There are methods for identifying ata keyboards as well. Check the Arch Wiki page listed in the references above for more info * There are methods for identifying atk keyboards as well. Check the Arch Wiki page listed in the references above for more info
* Defining a key to change is done with `KEYBOARD_KEY_<scancode>=<new keycode>` * Defining a key to change is done with `KEYBOARD_KEY_<scancode>=<new keycode>`
* `<scancode>` is the code we pulled from evtest earlier * `<scancode>` is the code we pulled from evtest earlier
* `<new keycode>` is the keycode we want to emit when the key is pressed. Names of keycodes are listed in `/usr/include/linux/input-event-codes.h`, and should be all lowercased in your udev config. * `<new keycode>` is the keycode we want to emit when the key is pressed. Names of keycodes are listed in `/usr/include/linux/input-event-codes.h`, and should be all lowercased in your udev config.