Josh Goebel

You should really test at lowest-level with `evtest`. (That's most useful) https://stackoverflow.com/questions/13129804/python-how-to-get-current-keylock-status Seems highly relevant... so it's easy-ish to query the device stats via evdev... but we can have multiple...

If you wanted to just play with that's possible you could add a function to `input.py` to export the currently advice devices - then you could import `input` into your...

> I think I've tried that in the past and it was basically a system-wide state change that was not isolated to one input device. I would not expect that...

> Just have to check the value of LED_NUML and try to keep track of it, I guess? Why should it be hard to keep track of? I assume it...

> do you mean every time the user presses a Numpad key? Yes. > I'm never sure in programming exactly what kind of thing is "no big deal" to perform...

I'm not sure I follow? I mean all the keys are "not used" until you run software and then whether they are used depends on what software you're running.

> Even now I think an optimization could occur on the x11 side as well. Yes, you can request that X inform you about window changes and then we could...

Please provide a more specific example than "some stuff". Do conditional maps not help?

Please see my last comment over in https://github.com/mooz/xkeysnail/issues/102 You could certainly add your own magic combos that toggle entire modmap/keymaps on and off...

It's not a bug, it's intentional. We deliver keystrokes the moment they are pressed because you never know WHAT might be listening to them (or what will follow)... we don't...