You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has happened to me before with other programs, where some use keycodes and other use keysyms.
For example, when I try to enter (which I enter on my laptop as Super + u with my Xmodmap, because my ctrl key is broken), rather than page up, neovim tells me "already at oldest change", as if I only pressed 'u'.
This is small, very platform specific, and frankly probably not on any list of priorities, but it would make this program useable in fringe cases like mine.
The text was updated successfully, but these errors were encountered:
I actually think this is relatively high priority because it represents an issue with the way that keyboard input is handled. However its unlikely to get solved until we switch to winit and the hopefully upcoming rewrite of the keyboard input api.
This has happened to me before with other programs, where some use keycodes and other use keysyms.
For example, when I try to enter (which I enter on my laptop as Super + u with my Xmodmap, because my ctrl key is broken), rather than page up, neovim tells me "already at oldest change", as if I only pressed 'u'.
This is small, very platform specific, and frankly probably not on any list of priorities, but it would make this program useable in fringe cases like mine.
The text was updated successfully, but these errors were encountered: