Normalise Space Cadet keycodes (#18864)
This commit is contained in:
parent
8e0945c822
commit
002b58f0e4
226 changed files with 419 additions and 403 deletions
|
@ -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.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue