Warp
Warp copied to clipboard
Keybindings are off for non QWERTY keyboard layouts
Describe the bug
I don't know if this is related to the missing option of customizing shortcuts (which already exists as an issue) but on my QWERTZ (german) keyboard layout Im not able to increase the font size via shortcut. It says `0` for reset and `=` for increase but thats actually the same key. 😅
If I switch to standard qwerty it works as expected.
To Reproduce
Steps to reproduce:
- Go to '...'
- Click on '...'
- Scroll down to '...'
- See error '...'
Expected behaviour
Would be nice to have the same way of font resizing like in any other app (cmd+'+' cmd+'-' and cmd+'0')
Screenshots
No response
Operating System
MacOS
OS Version
11.6
Additional context
Thanks for having me here :) love it so far!
I get the same issue when using dvorak-qwerty layout, it's supposed to have same keybindings as regular qwerty when used with command
key, but keybindings are off, as if the actual letter is used, and not the key
I have the same issue with a Cyrillic keyboard layout. Keyboard shortcuts that require Latin characters don't work at all.
Yes, I am having the same issue as @dderg on Mac OS 12.2.1 using the Dvorak - QWERTY ⌘ layout.
For other apps when I use command ⌘
+ a key it works as a QWERTY keyboard while holding down the command ⌘
key. But with warp unfortunately this doesn't work and I have to keep remembering to go back to full Dvorak mode in my head while holding the command ⌘
mode. iTerm doesn't have this problem so I think I'll have to keep using that until this issue is resolved.
AI experimental text to command keymap, ctrl+`, isn't possible on mac's azerty (pc) keyboard mode.
I have a similar issue, when trying to open the AI command search on a qwertz keyboard. The backtick is only accessible through pressing shift and so the command doesn't work.
I recently started experiencing a similar issue: previously history search would be triggered by Ctrl+R according to my current keyboard layout, now it is triggered only by Ctrl+R according to QWERTY.
The problem seems to be fixed for me with latest release
@japsu @FlorianRaichle is it working for yall as well Please comment and I'll reopen!
In v0.2022.08.08.09.21.stable_00, I am still experiencing this issue.
I recently started experiencing a similar issue: previously history search would be triggered by Ctrl+R according to my current keyboard layout, now it is triggered only by Ctrl+R according to QWERTY.
Thanks @japsu