Can tap-hold-next work with mouse events, or always press the modifier key regardless of hold duration?

[jtherrmann]

I'm trying to modify Caps Lock to act as esc if tapped and lctl if held.

The following:

(defsrc
  caps)

(deflayer qwerty
  @mycaps)

(defalias
  mycaps (tap-hold 130 esc lctl))

Is pretty good, but the timeout of 130 ms is too short for me, and the problem with increasing the timeout is then it takes too long for lctl to be pressed after pressing Caps Lock.

Using this alias:

(defalias
  mycaps (tap-hold-next 500 esc lctl))

solves the problem by immediately pressing lctl if a second key is pressed, except that it doesn't work with mouse events, so you still have to hold Caps Lock for the full 500 ms before you can do things like Ctrl+click or Ctrl+scroll.

Is there a way to make tap-hold-next work with mouse events? Assuming not, then is there a way to modify Caps Lock to have the following behavior?

1. As soon as Caps Lock is pressed, lctl is also pressed.
2. If Caps Lock is released within 500 ms, lctl is released and esc is tapped.
3. Otherwise, if Caps Lock is held longer than 500 ms, then lctl remains held until Caps Lock is released.

This would effectively have the same behavior as my tap-hold-next example, except that it would also work with mouse events because lctl would always be pressed regardless of how long Caps Lock was held.

I've been experimenting with uses of around to achieve this, but haven't got it to work yet.

[jtherrmann]

Nevermind, I just realized that my suggested workaround would not exactly solve the issue, because if you press Caps followed by a mouse event and then release Caps within 500 ms, esc is still tapped, which is not what you would want. So I think the only way to resolve this issue would be if kmonad were aware of mouse events.