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

Problem saving keybindings #25356

Open
Tekbr opened this issue Apr 26, 2017 · 2 comments
Open

Problem saving keybindings #25356

Tekbr opened this issue Apr 26, 2017 · 2 comments
Labels
feature-request Request for new features or functionality ux User experience issues
Milestone

Comments

@Tekbr
Copy link

Tekbr commented Apr 26, 2017

  • VSCode Version: 1.11.2 and 1.12.0 - insiders
  • OS Version: Windows 10

-- Sorry for the English, I used Google Translator --

When I set a shortcut, if you press Ctrl + k, the VSCode is waiting for a second combination. Which works great.

But if I press any keyboard and then Ctrl + k, this key takes the function of Ctrl + K and always waits for a second combination.

Example: n Ctrl + k

If you type a text and press n it is waiting for the second combination.

I know the same open multiple ports for shortcuts, but maybe one maybe a setting where I only limit use to Ctrl + k to receive a second combination.

My suggestion is (I do not know if it's possible):

1- Limit second combination only to Ctrl + k, or until the user changes.
2- Whenever you have this situation, reverse the shortcuts automatically, either on the new screen or manually. If you typed n Ctrl + k it should interpret or edit the file for Ctrl + k n
3 - Prevent saving the shortcut key if it is wrong or prevents it from working.

@alexdima
Copy link
Member

@Tekbr You can continue pressing in the define keybindings widget until you are happy with the result:

And you can press Escape if you are not happy with the result:

25356

@alexdima alexdima added ux User experience issues under-discussion Issue is under discussion for relevance, priority, approach labels Apr 26, 2017
@alexdima alexdima self-assigned this Apr 26, 2017
@alexdima alexdima added this to the Backlog milestone Apr 26, 2017
@Tekbr
Copy link
Author

Tekbr commented Apr 27, 2017

-- Sorry for the English, I used Google Translator --

@alexandrudima Maybe it does not make much sense to have suggested / questioned this, but I went to test a configuration and I ended up going through this situation. I figured I configured one thing and it came out another. I even thought my key was faulty, until I switched to another program and it still worked. I checked the keybindings file and saw what had done something wrong.

Maybe you have a better suggestion.

But maybe just block the use of:

1- A-Z Ctrl+k and 0-1 (including numeric keypad) Ctrl+k
Or
2- Ctrl + another key that has another function already configured except K + another key
Eg: Ctrl + J J for new file
Ctrl + J - opens the Toogle Panel - you can not open it until you change it.

Ctrl + k - I think it is already accepted by all or almost all for this second command function. Using Ctrl + alt + Shift + key key is very good too.

Well ... what I have suggested may be something impossible - I do not know - but maybe you can have a way to ease the situation.

@alexdima alexdima added feature-request Request for new features or functionality and removed under-discussion Issue is under discussion for relevance, priority, approach labels Apr 20, 2018
@alexdima alexdima removed their assignment Apr 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality ux User experience issues
Projects
None yet
Development

No branches or pull requests

2 participants