diff options
author | Ryan <fauxpark@gmail.com> | 2022-10-27 21:19:16 +1100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-10-27 11:19:16 +0100 |
commit | 002b58f0e4ea64eb5b06e36d988160bbb907cb83 (patch) | |
tree | 10ffe1f49d22b4ad6d660198da56782aae57e743 /users/gourdo1 | |
parent | 8e0945c82224ca2fdcc21eb7184520f879804fb6 (diff) |
Normalise Space Cadet keycodes (#18864)
Diffstat (limited to 'users/gourdo1')
-rw-r--r-- | users/gourdo1/autocorrect/autocorrection.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/users/gourdo1/autocorrect/autocorrection.c b/users/gourdo1/autocorrect/autocorrection.c index bc711016d9..dae62d37a2 100644 --- a/users/gourdo1/autocorrect/autocorrection.c +++ b/users/gourdo1/autocorrect/autocorrection.c @@ -71,7 +71,7 @@ bool process_autocorrection(uint16_t keycode, keyrecord_t* record) { break; // NOTE: Space Cadet keys expose no info to check whether they are being - // tapped vs. held. This makes autocorrection ambiguous, e.g. KC_LCPO might + // tapped vs. held. This makes autocorrection ambiguous, e.g. SC_LCPO might // be '(', which we would treat as a word break, or it might be shift, which // we would treat as having no effect. To behave cautiously, we allow Space // Cadet keycodes to fall to the logic below and clear autocorrection state. |