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
Describe the bug
I use a German keyboard layout. When I press Ctrl+Z, no undo happens. Instead, it happens when I press Ctrl+Y. This is because on a German keyboard layout, the Z and Y keys are swapped compared to American. And because Thunder Client assumes the American layout / uses hardcoded physical keys instead of inspecting the value of the keypress.
To Reproduce
Set your keyboard layout to German in your OS settings
Type something in a request URL bar
Press Ctrl+Z relative to the German layout. E.g. if you have an American keyboard, use the physical Y key.
No undo happens
Expected behavior
I expect Thunder Client to use the existing keyboard shortcuts for Undo / Redo set in VSCode. This would lead to my expected shortcuts to work: I have also set Ctrl+Y for Redo in VSCode, but Thunder Client uses Ctrl+Shift+Z, which becomes Ctrl+Shift+Y on a German keyboard.
Platform:
OS: Linux (Fedora 38)
vscode version: 1.84.4
extension version: v2.15.0
Are you using the free version/paid version/trial:
Free
The text was updated successfully, but these errors were encountered:
Describe the bug
I use a German keyboard layout. When I press Ctrl+Z, no undo happens. Instead, it happens when I press Ctrl+Y. This is because on a German keyboard layout, the Z and Y keys are swapped compared to American. And because Thunder Client assumes the American layout / uses hardcoded physical keys instead of inspecting the value of the keypress.
To Reproduce
Expected behavior
I expect Thunder Client to use the existing keyboard shortcuts for Undo / Redo set in VSCode. This would lead to my expected shortcuts to work: I have also set Ctrl+Y for Redo in VSCode, but Thunder Client uses Ctrl+Shift+Z, which becomes Ctrl+Shift+Y on a German keyboard.
Platform:
Are you using the free version/paid version/trial:
Free
The text was updated successfully, but these errors were encountered: