jtroo

I believe it is backwards compatible to make the existing `(unicode ...)` / `(🔣 ...)` action accept arbitrary characters, and seems like it would be good to reuse it for...

> By the way, what about inserting unicode text via clipboard (restoring the old clipboard values after) instead of typing char by char and having various app compatibility issues that...

The use case can now be implemented by added clipboard functionality. One can do DIY expansion with not-too-many characters using templates.

One way this can be achieved without turning off the service is to to use `lrld-next|prev` to cycle between configurations, which will be identical other than one having chords removed.

From a technical standpoint everything is working as intended, so really there's no bug. But there could certainly be a feature added that makes this more convenient and also perhaps...

Sounds like you might be able to achieve this today with some combination of: - [on-idle](https://github.com/jtroo/kanata/blob/main/docs/config.adoc#virtual-keys-aka-fake-keys) - [release-layer](https://github.com/jtroo/kanata/blob/main/docs/config.adoc#release-a-key-or-layer) - [switch with layer logic](https://github.com/jtroo/kanata/blob/main/docs/config.adoc#layer)

There is more recent functionality that might help with this: hold-for-duration.

Interesting. There's either a bug in Kanata where the code is comparing values incorrectly; which I have never reproduced; or your system has a bug in the monotonic time implementation....

Ah I see. You're using system time when you should instead use instant.

Unless there's a good reason, you should default to using monotonic time (instant) to measure durations. System time suffers from things like ntp corrections and any number of things that...