nsbgn

Ah, got it. Yes, in a macro, the down and up events are generated immediately. In most situations, this makes sense (it is a macro, after all --- not necessarily...

Ah, that's a good point. I was under the impression that a modifier (like a layer) never gets interpreted as retroactively applying to earlier keydown events (even if they're held),...

What are you trying to do? Bear in mind that the chord syntax `leftmeta+tab` is only triggered when you strike `leftmeta` and `tab` *at the same time*. It is not...

Thanks for the reproduction steps! I see the same issues (at least on the web version), but I don't think this is due to keyd not releasing the layer before...

If I understand correctly, the problem is that you want to emit `capslock` on tap, *except* if you press it again within some time. To disambiguate, we'd have to wait...

I can see the use of this, but I don't think it's easy to arrive at a general mechanism, because: if you hold `a+s` to get a `control`, and then...

Allowing arbitrary combinations of actions would make this a duplicate of https://github.com/rvaiya/keyd/issues/590. > z+c = layer(control+alt) > s+d+f = layer(shift+edit) The current solution is of course to just make layers...

Cf #651 and in particular https://github.com/rvaiya/keyd/issues/651#issuecomment-1925893039 #681 is also related, and I'd expect that if it makes it in, these two features should be achieved with the same mechanism. >`current`...

Try `rightshift = overload(shift, rightshift)` if your software requires the difference only when rightshift is tapped in isolation. Is that the case? Otherwise, you can use the following hacky solution:...

Different keyboards seem to implement the Copilot key slightly differently, huh. I don't know that this is currently possible to deal with gracefully, but here are a couple more ideas...