-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With Caps remapped, after emulating escape two times, it stops working #8
Comments
Oh, I'm running latest master. |
As you are probably aware, the option
I have been able to work around this issue by using a different XkbOption, namely, Unfortunately, it is not possible to then map the escape key to become a caps lock. As doing so results in two keys using the Is support for multiple keys using the same keysym something that could be added to xcape? If so, I may take a look at doing so when time permits. |
I have been remapping Caps Lock to Control using the GUI in GNOME and that always worked. I'm not sure how to reproduce the problem on my machine running Linux Mint. |
@benarmston Thanks for the info, I'm using @alols I believe you can do |
@dmedvinsky I assume this means I can close the issue now. |
When the computer first booted I had to press ctrl, otherwise xcape would not process single CapsLock press correctly. This was due to the confusion of having two keys produce the same keysym. The workaround is to assign the CapsLock to CapsLock, but remove the Lock modifier and add Ctrl modifier instead, then reconfigure xcape accordingly. Relevant tracker info: alols/xcape#62 Solution from: alols/xcape#8 (comment)
When the computer first booted I had to press ctrl, otherwise xcape would not process single CapsLock press correctly. This was due to the confusion of having two keys produce the same keysym. The workaround is to assign the CapsLock to CapsLock, but remove the Lock modifier and add Ctrl modifier instead, then reconfigure xcape accordingly. Relevant tracker info: alols/xcape#62 Solution from: alols/xcape#8 (comment)
Hello. I'm having some weird issue with
xcape
and Caps mapped to Control. The thing is, it works only for the first two presses, and then stops. It still works with normal Control key, but not with Caps, until restarted.Here's how I map Caps to Control:
Here's the output of
xcape --debug
:That is me running it and pressing Caps key three times in a row with a couple of seconds in between key presses and no other keys pressed.
The text was updated successfully, but these errors were encountered: