-
Notifications
You must be signed in to change notification settings - Fork 109
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
Non-Qwerty keyboards broken with current defaults #18
Comments
Do the default key bindings usually work for you in other software? Can you give an example of what's not working and what layout are you using? Thanks. |
I'm using azerty. |
The first thing I tried was to enter command mode, I got zoom-in instead, and had to grep the source to find what was going on. |
Hmmm, there's two ways to solve this that I can think of, but none are ideal:
|
Could you start by blessing winit over glfw? |
Unfortunately not - winit has significant problems on macOS. I’m not sure actually why the two handle keys differently - potentially there might be a way to have winit’s behavior in glfw. I’m looking into that now. |
I pushed a change to master that should fix this with |
I tried it, it works fine. |
I figured out that I need to enable the
winit
feature to get proper key mappings on my non-qwerty keyboard.Maybe this should be documented, or enabled by default.
The text was updated successfully, but these errors were encountered: