Failed to handle key ``: vimState.commandLine unexpectedly undefined
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
Don't really know. Just saw the dialog.
VSCodeVim version: 1.22.2
Stack trace
Error: Failed to handle key `
`: vimState.commandLine unexpectedly undefined
at assertDefined (/home/brian/.vscode/extensions/vscodevim.vim-1.22.2/src/util/util.ts:38:11)
at x.exec (/home/brian/.vscode/extensions/vscodevim.vim-1.22.2/src/actions/commands/commandLine.ts:28:5)
at x.execCount (/home/brian/.vscode/extensions/vscodevim.vim-1.22.2/src/actions/base.ts:230:20)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at j.actionToRecord [as runAction] (/home/brian/.vscode/extensions/vscodevim.vim-1.22.2/src/mode/modeHandler.ts:714:47)
at j.handledAsAction [as handleKeyAsAnAction] (/home/brian/.vscode/extensions/vscodevim.vim-1.22.2/src/mode/modeHandler.ts:663:43)
at j.text [as handleKeyEvent] (/home/brian/.vscode/extensions/vscodevim.vim-1.22.2/src/mode/modeHandler.ts:478:11)
at /home/brian/.vscode/extensions/vscodevim.vim-1.22.2/extensionBase.ts:359:73
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 with the stack-trace locations in src/actions/commands/commandLine.ts and trace the call chain through src/actions/base.ts and src/mode/modeHandler.ts. The report has no reproduction steps, so first identify a key sequence that triggers the undefined command line. Done means the sequence no longer produces the reported assertion error.
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
- Needs clarification
- Newbie friendliness
- 30/100