ordered chords (of length two)

[gerhard-h]

simulate

Here is a working attempt to have ordered chords (I had planned to request them as a new feature)

typing a then b the output will be "ab"
typing b then a the output will be "ba"

This can be useful in overruling home row mods, but maybe there are other applications (please share).

(deftemplate orderedchord (first second)
  (switch
    ((input-history real $first 2))  (macro $first $second) break
    ((input-history real $second 2)) (macro $second $first) break
    () (macro e r r o r) break ;; unreachable or you stuffed in the wrong letters 
  )
)
(defchordsv2
  (a b) (t! orderedchord a b) 150 first-release ()
)

[GrewHair]

Yeah! Love this thing! What i'm using is:

(defchordsv2
  (j f) (switch ((input-history real f 1)) esc break () (macro f j) break) 150 all-released ()
  (j k) (switch ((input-history real k 1)) esc break () (macro k j) break) 150 all-released ()
)

to send esc whenever i quickly type jf or jk (which is a vim cliche to exit the insert mode without having to reach for the escape key). But with Kanata I now have it system-wide, AND it doesn't have any side effects! So you can use it to, say, unfocus an input box or smth. Typing kj or fj just inputs these very letters.

The only hurdle is you have to type them real quick in succession. I personally wasn't able to tweak timeout and release behavior to accept slower typing and still trigger (while vim easily allows this) - either it's not possible or I can't wrap my head around the activation logic (tho it seems to be documented really thoroughly!), like maybe you necessarily have to keep both keys down for it to happen, idk. I was hoping the release behavior setting would help with this but i haven't really noticed much of a difference with either first-release or all-released for this use case.

Still it rules!

[rpnfan]

Isn't that a sequence? The whole idea about the chord is that the order is not relevant.

[gerhard-h]

"ordered chords" might be a cure in search of an illness :)

Isn't that a sequence?

Maybe not

• chords (should) have higher priority then for example tap-hold - for sequences I don't know.
• an intentional 2 key chord - even if ordered - has a different feel to it then the normal tap tap
• chordsv2 are easier to set up, e.g. don't require a leader key.
• for sequences I don't know if autorepeat is possible (for stuff like del or bsp)

@GrewHair but maybe sequences can solve your timing issues

[rpnfan]

Ah, the last point is an important one for sure. The keyboard remapping can get as complex as we (do not) want to... ;-)