vim.normalModeKeyBindingsNonRecursive is grayed out in settings.json
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
All the settings inside vim.normalModeKeyBindingsNonRecursive are grayed out and don't take effect.
When I type "vim.", there are many autocompletion options, but the nromalModeKeyBindingsNonRecursive doesn't appear.
To Reproduce
I don't know how to reproduce this issue. It happened a long time ago, and I just didn't care about it. But now, when I tried to fix it, nothing worked for me, even with a long chat with Copilot with ChatGPT 4o, etc.
Expected behavior
I expected when I press the key plus another key, like space, it would do the command specified... the problem is not in the leader key chosen, nor the keys assigned with it, tried different options, but nothing worked.
Screenshots
It also doesn't appear in the autocomplete options
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.28.1
- VSCode version: 1.95.3
- OS: Windows 11
Additional context
The Vim extension works fine for me in other files, the problem I have is only with this option: vim.normalModeKeyBindingsNonRecursive
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
Begin with the reported settings.json entry for vim.normalModeKeyBindingsNonRecursive and try to reproduce both the grayed-out state and missing autocomplete entry in VSCodeVim 1.28.1 on VS Code 1.95.3. Done means the setting is recognized and a minimal leader-key mapping takes effect; the issue currently provides no reproducible steps or named test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100