Failed to handle key `w`: command 'w' 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
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
VSCodeVim version: 1.24.3
Stack trace
Error: command 'w' not found
at b.k (vscode-file://vscode-app/c:/Users/DayaTadbir/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1668:3069)
at b.executeCommand (vscode-file://vscode-app/c:/Users/DayaTadbir/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1668:2985)
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 pressing w with VSCodeVim 1.24.3 in VS Code, then trace the key-command dispatch that produces command 'w' not found using the provided stack trace as context. Done means the w key works without that error and a regression test covers the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100