Failed to handle key `k`: command '<ESC>:w<CR>' not found
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
These are my bindings
"vim.insertModeKeyBindings": [
{"before": ["j", "k"], "commands": ["<ESC>:w<CR>"]},
{"before": ["k", "j"], "commands": ["<ESC>:w<CR>"]}
],
VSCodeVim version: 1.23.2
Stack trace
Error: command '<ESC>:w<CR>' not found
at v._tryExecuteCommand (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1696:3532)
at v.executeCommand (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1696:3414)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
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
No source file or test is named. Reproduce the vim.insertModeKeyBindings configuration in VS Code and trace how its commands entries are resolved, starting with the reported <ESC>:w<CR> command error. Done means the binding is handled without the command-not-found failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100