Add support for keyberon's HoldOnOtherKeyPress and PermissiveHold options for tap-hold about kanata HOT 8 CLOSED

Can try this out in the latest pre-release:
https://github.com/jtroo/kanata/releases/tag/v1.0.6-prerelease-2

from kanata.

Any progress on this?

When combined with a timeout, these are basically tap-hold-next and tap-hold-next-release in kmonad and I feel like they are superior to the usual tap-hold because they rely less on timing, making it far better for fast typers.

tap-hold-next is better for keys you would press either in isolation or as a modifier (e.g. Caps key -> ctrl/esc) and tap-hold-next-release is better for keys for writing where you also want something like home row mods (e.g. asdf also as ctrl shift alt super)

from kanata.

I haven't had anyone request it yet and I have no need for it myself which is why it hasn't been added.

It's marked as a good first issue in case someone wanted to add it themselves; it's not too complicated. If you'd like to try your hand at it, I can point you to the places in the code that might make sense to do the changes.

Otherwise if you'd like this functionality and don't have the knowledge/time to implement it, I can add it probably on the weekend.

from kanata.

Places to add code:

Should re-use most of this function but be able to change the config mode:

Should also edit cfg_samples/kanata.kbd to include examples of the new behaviours and document what they do.

from kanata.

I prefer PermissiveHold. I changed my version to use it always. I was planing to implement that, but was in doubt what could I name it: tap-hold-permissive seems long but ok. But tap-hold-otherkeypress seems ugly.

from kanata.

For naming, we could do something similar to the kmonad names since they seem reasonable:

• tap-hold-next is HoldOnOtherKeyPress
• tap-hold-next-release is PermissiveHold

Though to me, next is a bit ambiguous for what it means. Maybe more clear might be:

• tap-hold-press is HoldOnOtherKeyPress
• tap-hold-press-release is PermissiveHold

I'm not too attached to any particular name though. Other good ones can also be fine. More important is that the behaviour of these variations is well documented.

from kanata.

Yeah, tap-hold-press seems fine.

You could probably shorten tap-hold-press-release to just tap-hold-release since the press part is implied (and unimportant) when using release.

from kanata.

No problems with it so far. Thank you!

from kanata.