Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tap Term does not work for LT(1) #664

Open
tomwang2011 opened this issue Feb 6, 2024 · 4 comments
Open

Tap Term does not work for LT(1) #664

tomwang2011 opened this issue Feb 6, 2024 · 4 comments

Comments

@tomwang2011
Copy link

I have been trying to put LT(1) on spacebar such that tapping spacebar gives space and holding spacebar goes to layer 1.

According to QMK docs we should see something like: https://github.com/qmk/qmk_firmware/blob/master/docs/tap_hold.md#nested-tap-abba-idnested-tap where as long as I am within my tap term range, i press space then A gives me a. However if I hold space then tap A I should get left (I configured Layer 1 wasd to be directions).

As I am getting more left instead of a, I tried to increase the tap term under qmk settings. However even at an unrealistic 5000ms, I am still only getting left instead of a, so I think LT() probably doesn't work with tap term?

I tried the same when flashing qmk and it works fine.

@refact0r
Copy link

Try enabling and disabling Permissive Hold and Ignore Mod Tap Hold Interrupt and seeing if it changes anything.

@pmympmm
Copy link

pmympmm commented Apr 24, 2024

Hi,
I'm new to vial (my old keyboard used qmk and i didnt see the same - i am trying to use the same layout) but seeing something very similar to Tom. Did you figure it out @tomwang2011 ??

Vial 0.7.1 on linux/ubuntu.
my keyboard is a keyclicks ergo

I would upload my config but it has a bunch of macros and things with my name and other personal bits.

I type quite quickly and my home row is usually LT keys but what I find is that I often end up with keys from layers scattered into what I type.

I have also made tapping_term much much higher and it seems to have zero effect. eg setting it to 2000 doesn't change anything. This seems repeatable with ctrl and layer modifiers.

i've tried with combinations of permissive hold & ignore mod tap interrupt but get the same.

@sleeplesslord
Copy link

sleeplesslord commented May 13, 2024

I'm having the same problem with the Keychron Q11. The behavior of any key configured using mod tap is as if Permissive Hold is enabled even though it's disabled, and updating the tapping term doesn't seem to do anything. I tried enabling Ignore Mod Tap Interrupt and it seems to work the way I would expect now.

@ntubiolin
Copy link

I'm having the same problem with the Keychron Q11. The behavior of any key configured using mod tap is as if Permissive Hold is enabled even though it's disabled, and updating the tapping term doesn't seem to do anything. I tried enabling Ignore Mod Tap Interrupt and it seems to work the way I would expect now.

It works for me. Thanks!
Also found another explanation useful: https://reddit.com/r/olkb/comments/gmcb57/qmk_ignore_mod_tap_interrupt_documentation/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants