From 696744d5f27ff2ed014047407d5e259d27efe6aa Mon Sep 17 00:00:00 2001 From: Peter Cock Date: Fri, 24 Apr 2026 04:30:59 +0100 Subject: [PATCH] docs: Clarify combos interact with hold-tap's hold-while-undecided (#3335) --- docs/docs/keymaps/behaviors/hold-tap.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/docs/keymaps/behaviors/hold-tap.mdx b/docs/docs/keymaps/behaviors/hold-tap.mdx index 97464a9fd..2006a577e 100644 --- a/docs/docs/keymaps/behaviors/hold-tap.mdx +++ b/docs/docs/keymaps/behaviors/hold-tap.mdx @@ -437,6 +437,10 @@ If enabled, the hold behavior will immediately be held on hold-tap press, and wi }; ``` +:::warning[Interactions with combos] +If the key position that has the hold-tap assigned is _also_ used in any combos, the `hold-while-undecided` behavior isn't immediate with key-down, but waits until all those combo timeouts have expired. +::: + #### `hold-while-undecided-linger` If your tap behavior activates the same modifier as the hold behavior, and you want to avoid a double tap when transitioning from the hold to the tap, you can use `hold-while-undecided-linger`. When enabled, the hold behavior will continue to be held until _after_ the tap behavior is released.