Failed to handle key=i. Cannot read property 'start' of 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
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
VSCodeVim version: 1.18.9
Stack trace
TypeError: Failed to handle key=i. Cannot read property 'start' of undefined
at p.setCurrentMode (/home/andy/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:751311)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async F.setCurrentMode (/home/andy/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:697655)
at async F.runAction (/home/andy/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:708208)
at async F.handleKeyAsAnAction (/home/andy/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:707179)
at async F.handleKeyEvent (/home/andy/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:704015)
at async Object.promise (/home/andy/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:350696)
at async Object.runTasks (/home/andy/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:754577)
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 error when pressing key=i with VSCodeVim 1.18.9, then trace the reported setCurrentMode failure from the bundled out/extension.js stack trace back to the TypeScript source. The issue is done when the key no longer produces the undefined start error and the behavior is verified in the relevant test or reproduction case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100