Failed to handle key `K`: command 'extension.dash.specific' 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 'extension.dash.specific' not found
at S._tryExecuteCommand (vscode-file://vscode-app/c:/Users/28124/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1723:3532)
at S.executeCommand (vscode-file://vscode-app/c:/Users/28124/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1723: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
Start by reproducing the failed K key handling in VSCodeVim 1.24.3 and trace where the extension.dash.specific command is invoked. The payload names no source file or test; done means identifying the relevant command path and preventing the reported command-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100