Stops working after undefined time #121
Comments
|
Same problem here. In my case, Ctrl (which is triggered by the Caps Lock key, because I'm using the ctrl:swapcaps option, not sure if this matters here) also stops working. Any fix? |
|
xcape isn't being updated. i migrated to caps2esc and, more generally, to dual-function-keys. a bit harder to install, since not available on apt, but can be done with a little patience and this tutorial |
jfly
added a commit
to jfly/dotfiles
that referenced
this issue
Oct 18, 2021
Get rid of Xmodmap and xcape in favor of interception-tools and some
plugins for interception-tools. Some reasons why these are nicer:
- I now have spacebar as meta support!
- Xmodmap only applies to an X11 environment. When I'm in a TTY,
things are different.
- Chrome recently made some changes that cause it to not really
interact nicely with xmodmap:
https://bbs.archlinux.org/viewtopic.php?pid=1998285.
- xcape seems to stop working after some period of time:
alols/xcape#121, and it looks like it's no
longer maintained!
- xcape causes my ctrl key to send escape if I just tap it, which is
SUPER annoying.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i use a hold down space bar as a control key.
After an indefinite amount of time xcape stops working.
It can be hours up to a day.
It is still present as a process though.
Remedy is usually killing xcape and restarting, but i would also work without the kill.
This does not seem to be related to the usage of the mapped key, nor capslock nor escape like in similar issues.
The text was updated successfully, but these errors were encountered: