-
Notifications
You must be signed in to change notification settings - Fork 84
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
Numpad buttons don't work #106
Comments
What do you mean by "do not work"? |
The number keys, and +, -, /, and * keys produce no output, and the enter key does not execute the command (in the shell). |
Can you run "make check" which will produce "./test_input". Then run that as root from a command-line and show its output if you press the given keys. And please describe exactly which output happens for which key-presses. |
Strangely, different applications get different keys. ZSH gets nothing as I said above. /bin/login gets the correct keys, as does test_input. VIM, gets letters (p, q, r, s, t, u, v, w, x, and y). |
Can you please provide the output of ./test_input with a description what was reported on which key-presses? |
sym KP_End This output is correct. The bug appears to be in how kmscon reports these On 23 February 2014 15:11, David Herrmann notifications@github.com wrote:
|
Yepp, that depends on whether an applications sets the keypad-application-mode or not. This is done in libtsm src/tsm_vte.c in tsm_vte_handle_keyboard(). I'm not sure why that doesn't work as this is afaik the way to report these keys. Sadly, there's no real documentation so I'm not really sure what to do. The kmscon repository contains a "test_key" program (built by |
Perhaps related, if I start VIM from kmscon, pressing any key puts it into Replace mode. |
Something like that also reproduces in any curses "gui": num-keys work as arrow keys, "/" and "*" are swapped |
I realize this is probably way too late, but just in case anyone else runs across this like I did and spends several days wondering about it: I'm reasonably convinced this isn't a problem in kmscon, or libtsm, but is a problem in zsh (as mentioned by the OP in the comment above). More specifically it's an issue in a probable extension (like oh-my-zsh or countless others) that use the smkx/rmkx sequences to place the terminal in application mode. Firing up a bash, dash, or a "raw" zsh (with "zsh +d -f") on my system resulted in the keypad working just fine, but it displayed the exact behaviour noted above (right down to the precise same test_input output) under my "usual" zsh environment. There's a lot more discussion and workarounds to be found, e.g.: https://superuser.com/questions/742171/zsh-z-shell-numpad-numlock-doesnt-work Some of those may appear Mac OS specific, but it's all the same underlying issue with smkx/rmkx. There's several workarounds to pick from the links above; disable the config setting application mode for zle (zsh's line editor), use bindkey to override the output, or something much more complex (like the PR in the last link). Ultimately though, I think this could be closed as "not a problem in kmscon" (or libtsm for that matter). |
In kmscon, the numbers (with numlock on), +, -, *, /, ., and enter keys in the numpad area do not work.
The text was updated successfully, but these errors were encountered: