aboutsummaryrefslogtreecommitdiff
path: root/docs/feature_key_lock.md
diff options
context:
space:
mode:
authorDrashna Jael're <[email protected]>2022-10-24 23:28:56 -0700
committerDrashna Jael're <[email protected]>2022-10-24 23:28:56 -0700
commiteeb3f9c04346da4f387f1beb439f558a82fcb95c (patch)
tree7b997f5a62d862dac576bb04eb49a1023ef5af0c /docs/feature_key_lock.md
parente3594135012aa8c8bc309bf43aaa958f3135a30a (diff)
parentf100de88e524633d4f7b35602b37ad6a76044f1d (diff)
downloadqmk_firmware-eeb3f9c04346da4f387f1beb439f558a82fcb95c.tar.gz
qmk_firmware-eeb3f9c04346da4f387f1beb439f558a82fcb95c.zip
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs/feature_key_lock.md')
-rw-r--r--docs/feature_key_lock.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_key_lock.md b/docs/feature_key_lock.md
index d5ad1708c7..1acee524da 100644
--- a/docs/feature_key_lock.md
+++ b/docs/feature_key_lock.md
@@ -16,7 +16,7 @@ First, enable Key Lock by setting `KEY_LOCK_ENABLE = yes` in your `rules.mk`. Th
## Caveats
-Key Lock is only able to hold standard action keys and [One Shot modifier](one_shot_keys.md) keys (for example, if you have your Shift defined as `OSM(KC_LSFT)`).
+Key Lock is only able to hold standard action keys and [One Shot modifier](one_shot_keys.md) keys (for example, if you have your Shift defined as `OSM(MOD_LSFT)`).
This does not include any of the QMK special functions (except One Shot modifiers), or shifted versions of keys such as `KC_LPRN`. If it's in the [Basic Keycodes](keycodes_basic.md) list, it can be held.
Switching layers will not cancel the Key Lock. The Key Lock can be cancelled by calling the `cancel_key_lock()` function.