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

AZERTY layout is ignored in vscode shortcuts #321

Closed
vlebourl opened this issue Sep 24, 2021 · 4 comments
Closed

AZERTY layout is ignored in vscode shortcuts #321

vlebourl opened this issue Sep 24, 2021 · 4 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@vlebourl
Copy link

Problem/Motivation

With an AZERTY keyboard, hitting Cmd-Z (on a mac) closes the tab instead of doing "undo".

Expected behavior

Cmd-Z is mapped to Undo, so expecting it.

Actual behavior

Cmd-Z is closing the tab

Steps to reproduce

Hit Cmd-Z on an AZERTY keyboard

Proposed changes

Further test

The editor seems to know the layout, but trying to change the shortcuts in the preferences doesn't. In the preferences, the layout seems to always be QWERTY.

@vlebourl vlebourl changed the title AZERTY AZERTY layout is ignored in vscode shortcuts Sep 24, 2021
@vlebourl
Copy link
Author

I had a question in the forum about it, but I do believe it's a bug, so here it is. Forgive me if it's not the place...
https://community.home-assistant.io/t/home-assistant-community-add-on-visual-studio-code/107863/444

@vlebourl
Copy link
Author

Hey, sorry to insist, but this is super annoying having the current tab closed when trying to "undo"... I've tried modifying the keybindings, but it's not working either... Any way I can help fix this?
Cheers

@grischard
Copy link

This might be related to #320

@github-actions
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Nov 27, 2021
@github-actions github-actions bot closed this as completed Dec 5, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jan 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

2 participants