-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Aligned keybindings with VSCode #5621
Conversation
Signed-off-by: Josh Pinkney <joshpinkney@gmail.com>
@vince-fugnitto Could you test whether the keybinding widget still shows context and source properly? There was a merge conflict with it. If it is fine please approve and we can merge it. |
It seems to work correctly, but the Example:
[
{
"command": "core.close.tab",
"keybinding": "alt+a",
"context": ""
},
{
"command": "-core.close.tab",
"keybinding": "alt+w",
"context": ""
}
]
[
{
"command": "-core.close.tab",
"keybinding": "alt+w",
"context": ""
}
] Is it outside the scope of the PR? |
@vince-fugnitto I've seen it, but it does not seem to break keybindings handling? Does it? |
I'm not sure, but I do know that if I have a custom keybinding that I set, then reset it, I lose the original keybinding due to the removal rule. For example:
|
@vince-fugnitto I thought |
Sorry if I'm being confusing, when I mean removed I mean that I can no longer use that keybinding as a user, the command becomes useless. I attempt to close tabs using the default keybinding and it no longer works (since it exists in the keymaps as a removal rule). |
@vince-fugnitto tried and was able to reproduce your issue, could you please comment it on the original PR #5326, it should be taken care of before merging. I'm closing this PR. |
fixed #5303
It's rebase of #5326, since the original PR is opened from a fork without right to commit for maintainers.