From 3d9a72e1cebf8c5e11994525ce955d24a4044685 Mon Sep 17 00:00:00 2001 From: "jmding@gmail.com" Date: Mon, 13 Sep 2021 02:53:02 +0000 Subject: [PATCH] add ntoe about tapping term to docs (that was mistakenly left out of the prev commit --- docs/docs/behaviors/hold-tap.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/docs/behaviors/hold-tap.md b/docs/docs/behaviors/hold-tap.md index a9ca5b0b..7c9cfb96 100644 --- a/docs/docs/behaviors/hold-tap.md +++ b/docs/docs/behaviors/hold-tap.md @@ -135,6 +135,8 @@ Meanwhile, the sequence `(cht_down, E_down, E_up, W_down, W_up cht_up)` produces Conditional hold-taps can be useful with home-row modifiers for example. By setting `hold-enabler-keys` to include only the keys controlled by the opposite hand, conditional hold-taps can prevent one-handed "rolls" from accidentally triggering hold behaviors. +Note that while for regular hold-tap behaviors a shorter `tapping-term` encourages hold decisions, the opposite is true for conditional hold-tap behaviors. For conditional hold-taps, a shorter `tapping-term` actually encourages tap decisions. This is because when the `tapping-term` expires, this triggers the behavior to decide as either a tap or a hold. But if the user has not yet had time to press one of the `hold-enabler-keys`, then the behavior will decide as a tap. Shortening the `tapping-term` thus gives the user less time to press one of the `hold-enabler-keys` to produce a hold behavior. + #### Comparison to QMK The hold-preferred flavor works similar to the `HOLD_ON_OTHER_KEY_PRESS` setting in QMK. The 'balanced' flavor is similar to the `PERMISSIVE_HOLD` setting, and the `tap-preferred` flavor is similar to `IGNORE_MOD_TAP_INTERRUPT`.