diff options
author | precondition <[email protected]> | 2022-12-13 12:20:07 +0100 |
---|---|---|
committer | GitHub <[email protected]> | 2022-12-13 22:20:07 +1100 |
commit | 515dd18c2801663bbac0e59f683c2a93e4bd9b1a (patch) | |
tree | a60fa641a1d5e0e3ff08fbb0a6718c8aa5280f15 /docs/feature_auto_shift.md | |
parent | ca13734f912e64c632daf816e700b1b176d0ac8e (diff) | |
download | qmk_firmware-515dd18c2801663bbac0e59f683c2a93e4bd9b1a.tar.gz qmk_firmware-515dd18c2801663bbac0e59f683c2a93e4bd9b1a.zip |
Remove IGNORE_MOD_TAP_INTERRUPT_PER_KEY in favour of HOLD_ON_OTHER_KEY_PRESS_PER_KEY (#15741)
Diffstat (limited to 'docs/feature_auto_shift.md')
-rw-r--r-- | docs/feature_auto_shift.md | 11 |
1 files changed, 1 insertions, 10 deletions
diff --git a/docs/feature_auto_shift.md b/docs/feature_auto_shift.md index d3437a9c60..1719807e26 100644 --- a/docs/feature_auto_shift.md +++ b/docs/feature_auto_shift.md @@ -281,16 +281,7 @@ Tap Hold Configurations work a little differently when using Retro Shift. Referencing `TAPPING_TERM` makes little sense, as holding longer would result in shifting one of the keys. -`IGNORE_MOD_TAP_INTERRUPT` changes *only* rolling from a mod tap (releasing it -first), sending both keys instead of the modifier on the second. Its effects on -nested presses are ignored. - -As nested taps were changed to act as though `PERMISSIVE_HOLD` is set unless only -`IGNORE_MOD_TAP_INTERRUPT` is (outside of Retro Shift), and Retro Shift ignores -`IGNORE_MOD_TAP_INTERRUPT`, `PERMISSIVE_HOLD` has no effect on Mod Taps. - -Nested taps will *always* act as though the `TAPPING_TERM` was exceeded for both -Mod and Layer Tap keys. +`RETRO_SHIFT` enables [`PERMISSIVE_HOLD`-like behaviour](tap_hold.md#permissive-hold) (even if not explicitly enabled) on all mod-taps for which `RETRO_SHIFT` applies. ## Using Auto Shift Setup |