diff options
| author | Okke Formsma <okke@formsma.nl> | 2020-09-02 22:30:09 +0200 |
|---|---|---|
| committer | Pete Johanson <peter@peterjohanson.com> | 2020-11-03 00:19:37 -0500 |
| commit | 4f258efbf1602e212a808cc10915050a1b46e140 (patch) | |
| tree | ed7601514e31895139ab91314610b2d570b1d326 /docs | |
| parent | a9e729b427800fab230fc1fcdacd3cbdb6bedc19 (diff) | |
initial implementation for modifiers
https://github.com/zmkfirmware/zmk/issues/86
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/docs/feature/keymaps.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/docs/feature/keymaps.md b/docs/docs/feature/keymaps.md index 56fc2cc..a322336 100644 --- a/docs/docs/feature/keymaps.md +++ b/docs/docs/feature/keymaps.md @@ -68,7 +68,7 @@ In this case, the `A` is actually a define for the raw HID keycode, to make keym For example of a binding that uses two parameters, you can see how "mod-tap" (`mt`) is bound: ``` -&mt MOD_LSFT D +&mt LSFT D ``` Here, the first parameter is the set of modifiers that should be used for the "hold" behavior, and the second @@ -92,7 +92,7 @@ The top two lines of most keymaps should include: The first defines the nodes for all the available behaviors in ZMK, which will be referenced in the behavior bindings. This is how bindings like `&kp` can reference the key press behavior defined with an anchor name of `kp`. -The second include brings in the defines for all the keycodes (e.g. `A`, `NUM_1`, `M_PLAY`) and the modifiers (e.g. `MOD_LSFT`) used for various behavior bindings. +The second include brings in the defines for all the keycodes (e.g. `A`, `NUM_1`, `M_PLAY`) and the modifiers (e.g. `LSFT`) used for various behavior bindings. ### Root devicetree Node |