Unable to set vscodevim default settings through keymap extension
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
- I am writing a VS Code extension
lunarkeymap - The extension is unable to contribute defaults for vscode vim
Here are the error messages:
- Cannot register configuration defaults for 'vim.normalModeKeyBindingsNonRecursive'. Only defaults for machine-overridable, window, resource and language overridable scoped settings are supported.
- Cannot register configuration defaults for 'vim.visualModeKeyBindingsNonRecursive'. Only defaults for machine-overridable, window, resource and language overridable scoped settings are supported.
- Cannot register configuration defaults for 'vim.insertModeKeyBindings'. Only defaults for machine-overridable, window, resource and language overridable scoped settings are supported.
To Reproduce
Steps to reproduce the behavior:
- Generate new VS Code keymap extension
- Edit
package.json - Add new
"contribute"object - Add new
"configurationDefault"object - Add
{
"before": ["<C-h>"],
"commands":["workbench.action.navigateLeft"]
},
{
"before": ["<C-l>"],
"commands": ["workbench.action.navigateRight"]
},
],
- Add the extension locally
- Test the extension
Expected behavior
- vscodevim is able to be configured via any vscode keymap extension
Screenshots
Environment (please complete the following information):
- Extension (VsCodeVim) version:
- VSCode version: 1.80.0
- OS: Windows and Linux
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the configurationDefault entries in package.json with the listed vim.normalModeKeyBindingsNonRecursive, vim.visualModeKeyBindingsNonRecursive, and vim.insertModeKeyBindings settings. Check the VS Code configuration-scope behavior that produces the reported errors; done means establishing supported behavior and implementing or documenting a clear resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100