Josh Goebel

You could test the basic functionality without an X server but to test the actual conditional window name stuff yeah you need a GUI.

How I originally imagined this is it would only apply to regular keypresses (A-Z, etc), not modifier [keys]... as it would be handled at the very bottom of the stack......

Wouldn't you just likely use: ```py # nested map { Key.ANY: passthru # and return by default } ``` ?

Not sure what you're calling a macro... `passthru` would be another ComboHint... it's not a variable... > Key.ANY: None, Well, that would return by default... so you might want `Key.ANY:...

Yeah, can't do that... the outputs are all straight out - they purposely do not loop back thru the input pipeline. You can't write something to the output that will...

> That's 25 different lines in 25 different nested keymaps. This is why loops were invented... :-) Things within things are exactly when you should prefer loops though... > If...

> If the "passthru" ComboHint would cause the input to go through without being transformed into something else, why would that combo not be able to activate the same or...

Can you solve this by ordering the key maps? Put the key maps you need to exit from first. Then a dummy key map with a conditional. And then all...

Well your actions are limited but you could easily toggle some state which could have all sorts of effects on active keymaps.

Show me what you're playing with... you may need a small state machine to keep track of what state the system is currently in - so you known which keymaps...