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

tui: Numpad doesn't work anymore #7630

Closed
to-huu opened this issue Nov 24, 2017 · 12 comments
Closed

tui: Numpad doesn't work anymore #7630

to-huu opened this issue Nov 24, 2017 · 12 comments
Labels
bug-regression wrong behavior that was introduced in a previous commit (please bisect) input tui
Milestone

Comments

@to-huu
Copy link

to-huu commented Nov 24, 2017

Hello,
i upgraded from nvim v.2.0 and now the numpad isn't working anymore.
I've tried to remap, but without success.

  • nvim --version: NVIM v.0.2.3-24-gd9b3ebfed
  • Operating system/version: Arch Linux49 (4.9.63-1)
  • Terminal name/version:urxvt v9.22
  • $TERM:rxvt-unicode-256color

Kind regards

@glacambre
Copy link
Member

Hello,
This is a surprising issue. Does the numpad work in your shell? If yes, what happens when you press C-v+ a numpad number in insert mode in neovim? Does the same thing happen in your shell?

@gabbage
Copy link

gabbage commented Nov 26, 2017

Hello,
i'm having the same problem. C-v and a numpad character does nothing in nvim, but prints most of the numpad characters in the shell. oddly, only 123456 and not 789. but without C-v it works in the shell.

except for the OS (Debian with 4.9.30-2 kernel), i'm having the same specs.
cheers

@to-huu
Copy link
Author

to-huu commented Nov 26, 2017

Hello,
in the shell the numpad works fine (with and without C-v). In neovim nothing happens with C-v either.
Kind regards

@justinmk
Copy link
Member

I'm working on restoring :set termcap so we can diagnose TUI issues a bit better. Will revisit this then.

@justinmk justinmk added the bug-regression wrong behavior that was introduced in a previous commit (please bisect) label Dec 1, 2017
@justinmk justinmk added this to the todo milestone Dec 1, 2017
@justinmk
Copy link
Member

justinmk commented Dec 1, 2017

@sputny if you are able to build from source, could you try #7653 and post the log file from:

./build/bin/nvim -V3log

@justinmk justinmk added the needs:response waiting for reply from the author label Dec 4, 2017
@to-huu

This comment has been minimized.

@justinmk justinmk removed the needs:response waiting for reply from the author label Dec 8, 2017
@justinmk
Copy link
Member

  key_a1                    ka1        = <Esc>Ow
  key_a3                    ka3        = <Esc>Oy
  key_b2                    kb2        = <Esc>Ou
  key_c1                    kc1        = <Esc>Oq
  key_c3                    kc3        = <Esc>Os

This means Nvim (and your terminfo) thinks that <Esc>Ow is "keypad 1". That usually means "7" or "Home" on the numpad. Please try this, using the numpad in all cases:

  • In your shell (bash), type CTRL-v then <Home>. What does it print?
  • In your shell (bash), type CTRL-v then 7. What does it print?
  • In Nvim, in insert-mode, type CTRL-v then <Home>. What does it print?
  • In Nvim, in insert-mode, type CTRL-v then 7. What does it print?

Also if anyone can try reverting 5701165 to see if that helps, that would be useful.

@justinmk justinmk changed the title Numpad doesn't work anymore (Neo2 keyboard layout) tui: Numpad doesn't work anymore Dec 10, 2017
@to-huu
Copy link
Author

to-huu commented Dec 12, 2017

Hey all,
that happens:

  • bash, CTRL-v then <Home> prints ^[[7~
  • bash, CTRL-v then <7> prints7
  • Nvim, CTRL-v then <Home> prints <home>
  • Nvim, CTRL-v then <7> prints ^

@justinmk

This comment has been minimized.

@to-huu

This comment has been minimized.

@to-huu

This comment has been minimized.

@justinmk
Copy link
Member

justinmk commented Mar 29, 2019

Resolution/Summary

#9793 f6fb370 (Nvim 0.4.0) adds support for keypad keys.


Locked to keep the summary visible. You can always chat or open a ticket if you have new information/topics to discuss.

@neovim neovim locked as resolved and limited conversation to collaborators Mar 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug-regression wrong behavior that was introduced in a previous commit (please bisect) input tui
Projects
None yet
Development

No branches or pull requests

4 participants