-
-
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
Error when remapping to commands with name starting with "extension." #3307
Comments
Interesting. Do you mind trying an experiment? Can you try explicitly activate the extension by calling the |
Yes, I have the same problem. |
With #3296, we added a check on remapped commands to ensure that they were 'valid' commands. We get a list of valid commands through VS Code's |
Ah, ok. My suspicion was true. We load the valid commands on startup here ( Line 316 in d1261f2
insertSemicolon is not a valid command. Once you explicitly activate that extension, it'll then be OK. We'll need a code change.
|
fix: log warning if remapped command does not exist. closes #3307
Nothing needed to be done. After vscode was updated to 1.30.2, the problem was fixed. |
🤔 Upgrading from VS Code 1.30.1 to 1.30.2 didn't fix it for me: {
"before": ["<leader>", "i"],
"commands": [
"python.sortImports"
]
}
|
Describe the bug
I just got this bug one or two weeks ago, as remapping to commands starting with
exentension.
was working fine.The command in question can be found via the shortcut settings and works fine with
![image](https://user-images.githubusercontent.com/30693990/50548563-78ca8a00-0c4f-11e9-8bbd-144fe71de2cb.png)
ctrl+,
To Reproduce
Steps to reproduce the behavior:
chrisvltn.vs-code-semicolon-insertion
Expected behavior
In 3. from steps to repro, the command should execute
Screenshots
![image](https://user-images.githubusercontent.com/30693990/50548658-a237e580-0c50-11e9-86f3-6a245e7d5956.png)
Environment (please complete the following information):
Additional context
normalModeKeyBindings
as well, still same errorThe text was updated successfully, but these errors were encountered: