Skip to content
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

Regression: dvorak-qwerty commands keyboard layout no longer works correctly #23986

Closed
darknoon opened this issue Apr 6, 2017 · 8 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@darknoon
Copy link

darknoon commented Apr 6, 2017

  • VSCode Version: Code 1.11.0 (9122ec4, 2017-04-05T20:52:01.201Z)
  • OS Version: Darwin x64 16.5.0
  • Extensions:
Extension Author Version
vscode-eslint dbaeumer 1.2.8
flow-for-vscode flowtype 0.5.0
JavaScriptSnippets xabikos 1.4.0
ReactSnippets xabikos 1.2.1

Steps to Reproduce:

  1. Press command-s key on keyboard, should save
  2. Action is Open not save :(

Started happening when I updated to the latest version

@darknoon
Copy link
Author

darknoon commented Apr 6, 2017

Seems to dup #23964

@darknoon
Copy link
Author

darknoon commented Apr 6, 2017

Appears related to work on #17521

@gyzerok
Copy link
Contributor

gyzerok commented Apr 6, 2017

Are there any way to workaround it or downgrade VSCode to the previous version meanwhile?

@alexdima
Copy link
Member

alexdima commented Apr 6, 2017

Workaround: switch VS Code to dispatch based on key code again. Add the following setting:
"keyboard.dispatch": "keyCode" and restart VS Code


I would really like to understand your setup. I'm sorry for the breakage, I am really trying to get this right. Could you please explain like I'm five how to get into your setup (I thought the whole point of dvorak is that its not qwerty -- the name contradicts itself, r cannot be both between o and a and between e and t), and what key combination fails. It would also help to attach here what our C++ node module detects (open an editor, press F1 > Developer: Inspect Keyboard Mappings save the output to a file and attach here).

@alexdima
Copy link
Member

alexdima commented Apr 6, 2017

Duplicate of #23964

@alexdima alexdima closed this as completed Apr 6, 2017
@alexdima alexdima added the *duplicate Issue identified as a duplicate of another issue(s) label Apr 6, 2017
@darknoon
Copy link
Author

darknoon commented Apr 6, 2017

@alexandrudima thanks a lot for following up with the workaround! after I set that setting, my keybindings are working again!

@darknoon
Copy link
Author

darknoon commented Apr 6, 2017

@alexandrudima I understand this is a little confusing. It's a keyboard layout that AFAIK doesn't exist on windows. Basically, it's Dvorak except when you're holding down the command (⌘) key, where it reverts back to qwerty. This is done because all of the key commands in macOS are designed ergonomically rather than by what the letter is.

So it would defeat the purpose of DVORAK if your commands had their ergonomics messed up by it, so I used this hybrid (which has been supported since ancient times on mac os classic etc).

@crwang
Copy link

crwang commented Apr 8, 2017

I'm getting the same thing on my Mac.

When I used windows, I used to use this: https://github.com/bradfeehan/Dvorak-QWERTY-Ctrl to do the same thing that the Mac supports for their Dvorak-Qwerty keyboard setup.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants