-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Allowing user to selectively disable some key combos #1425
Conversation
…ey combinations with a config option
package.json
Outdated
}, | ||
{ | ||
"key": "ctrl+p", | ||
"command": "extension.vim_ctrl+p", | ||
"when": "suggestWidgetVisible && vim.useCtrlKeys" | ||
"when": "suggestWidgetVisible && vim.use<C-p> vim.useCtrlKeys" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops
package.json
Outdated
}, | ||
{ | ||
"key": "ctrl+n", | ||
"command": "extension.vim_ctrl+n", | ||
"when": "suggestWidgetVisible && vim.useCtrlKeys" | ||
"when": "suggestWidgetVisible && vim.use<C-n> vim.useCtrlKeys" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops
…ted when you update config without needing to restart
…guration for reference
This LGTM. It's really interesting that properties in package.json can include < and > characters. |
Yea that felt a bit crazy, but if it works it works. I figured it wasn't any worse than vim.useCtrl+k etc, and then atleast the nomenclature is the same throughout our remappings etc |
I like this. PR for #1424
example config option that may be handy on windows for some
I would like to have it all in configuration.ts so that it can happen without a vscode restart so that will be next. Then trying to clean it up some more and make sure all of our keys in package.json are handled (only modifier key combos I think will be part of this)