Closed ibabushkin closed 7 years ago
Note to self - I probably should check this behaviour without Xephyr
.
Can't reproduce in normal use.
It might make sense to allow for ignoring specific modifiers, such as {caps,num}lock
to avoid issues like these
The feature mentioned above is implemented, so this issue can be considered fixed.
When we start
Xephyr
, activate NumLock, start the window manager to connect to theXephyr
-instance, deactivate NumLock, the events we receive "pretend" that NumLock is still on.