From 67fd4e6b7afe5515b67f153723f57beabbebe25e Mon Sep 17 00:00:00 2001 From: Joel Challis Date: Mon, 24 Oct 2022 23:29:23 +0100 Subject: [DOCS] Use correct OSM arguments (#18835) --- docs/feature_key_lock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/feature_key_lock.md') diff --git a/docs/feature_key_lock.md b/docs/feature_key_lock.md index 7681394229..1b02c7c291 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. -- cgit v1.2.3