-
Notifications
You must be signed in to change notification settings - Fork 26
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
Hotkeys don't work outside of English layout #86
Comments
Yeah, there is such a problem. I think it is not solvable because users may have weird keyboard layouts. That's why we kinda decided to ignore the problem for the time being. Perhaps @handlerug can save the day |
I think we should just open the hotkey list (i.e. bind it to |
I think I want to include йцукен hotkeys too now. |
I still see the better option in implementing these through |
Yeah, it's probably good, I'll take a look. |
Not actually fixed, tested on Chrome on Windows. |
How to reproduce: try pressing
h
on any hypha page orCtrl-B
in editor, when using Russian or another non-Latin keyboard layout.I've localized it to
static/shortcuts.js
, as its code useskey
property to retrieve the pressed key, however we also have layout-agnosticcode
property (andwhich
, now deprecated). We can redo the code to use these values for hotkeys (convertKey*
andDigit*
keys, and maybe symbols, and cast everything else).As an alternative, we could enable users to add their own shortcuts and partly circumvent the problem (also improving QoL for user JS plugins). Or do both proposed things.
That is actually a common problem in a variety of software (e.g. Vim, and even Github).
The text was updated successfully, but these errors were encountered: