nsbgn

Variants of this have been discussed, see for example https://github.com/rvaiya/keyd/issues/879 (perhaps there is one that more closely matches your use case), but I don't remember if there's one specifically tackling...

That depends on what key the physical Fn key emits. You can check with `keyd monitor`. Often, an Fn key doesn't actually emit anything on its own, it just changes...

What is the keyd monitor output of the keys? Is it always with the meta+shift modifiers? Based on your example, I would expect something like this to work: ``` [main]...

That sequence should indeed emit `C-a`. Are you sure your config is correct? What is your full config and the output in the logs? (`journalctl -u keyd` on systemd-based systems)

Ah, gotcha. The problem is not with the `capslock = overload(...)` but with the `a = overloadt(...)`. When you tap `a`, it will emit the macro `a`, but it either...

> Oh, I guess this behaves as a priority, where if control is already typed then it sends C-a instead of the overloadt. So I might want to do it...

You would have to add bindings like `y = macro(a y)` inside the `arrows` layer: unbound keys do fall through other layers by default, but they still also have to...

It just occurred to me that making an `[empty]` layer and binding `y = swapm(empty, macro(a y))` would make it work for longer overlaps too. Still not ideal, but one...

> Any idea why it works for all of them but this one? `rightalt` is a key name. `altgr` is the corresponding layer name. So try `[altgr]` ;) > most...