Resolve ambiguity in documentation
No modifiers will be preserved could be misunderstood as no modifier, including those that aren't part of `mods` will be preserved.
This commit is contained in:
parent
53ad3ad364
commit
e96514db17
1 changed files with 1 additions and 1 deletions
|
@ -70,7 +70,7 @@ mods = <(MOD_LGUI|MOD_LSFT|MOD_RGUI|MOD_RSFT)>;
|
|||
|
||||
`keep-mods`
|
||||
|
||||
When a modifier specified in `mods` is being held, it won't be sent along with the morphed keycode unless it is also specified in `keep-mods`. By default `keep-mods` equals `0`, which means no modifiers will be preserved.
|
||||
When a modifier specified in `mods` is being held, it won't be sent along with the morphed keycode unless it is also specified in `keep-mods`. By default `keep-mods` equals `0`, which means no modifier specified in `mods` will be sent along with the morphed keycode.
|
||||
|
||||
For example, the following configuration morphs `LEFT_SHIFT` + `BACKSPACE` into `DELETE`, and morphs `RIGHT_SHIFT` + `BACKSPACE` into `RIGHT_SHIFT` + `DELETE`.
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue