Skip to content
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

Simulating Control+w sometimes inserts a bunch of Ws #10

Closed
noctuid opened this issue Dec 2, 2017 · 2 comments
Closed

Simulating Control+w sometimes inserts a bunch of Ws #10

noctuid opened this issue Dec 2, 2017 · 2 comments

Comments

@noctuid
Copy link

noctuid commented Dec 2, 2017

I have this in my config:

"shiftlevels": [ "None", "Shift", "AltGr", "Shift+AltGr", "Extend" ],
....
{ "pos": "W", "letters": [ "w", "W", "`", "~", "Control+w" ] },

I use Control+w for "backspace a word" functionality in a lot of applications. Most of the time this works fine, but maybe 5% of the time, after the deleting a word a bunch of ws will be continuously inserted (even though I'm not pressing any keys). It may also simulate C-w a few times and delete more than one word. (I'm using XKB)

@39aldo39
Copy link
Owner

39aldo39 commented Dec 2, 2017

This probably isn't caused by the XKB config, since it can't even express multiple key presses.

I think that your w key sometimes remains pressed for a short time, which may be caused by some program or your keyboard. If you still have Extend down, it will execute C-w a few times. If you don't, it will execute w a few times. This also happens if you manually hold w down for a little longer.

If this is the case, it is probably fixed by disabling autorepeat or by increasing its delay time. But you obviously would lose autorepeat, which you may not want. You can disable it by executing xset r off (xset r on turns it on again). You can also disable it just for the w key by executing xset -r 25. The delay time can be changed by executing xset r rate $milliseconds.

@noctuid
Copy link
Author

noctuid commented Dec 5, 2017

I can't intentionally trigger this behavior regardless of how long I hold down either key, but after disabling repeat for w, I haven't noticed the issue anymore. For whatever reason, this doesn't happen with any other key and doesn't happen with w if I bind it to something different. I'll continue to test, but I think disabling repeat solved the issue.

Edit: this actually happens when I bind w to other keys. I never had this issue before using klfc, but I'm guessing that's just a coincidence.

@noctuid noctuid closed this as completed Dec 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants