Failed to handle key=s. Cannot read property 'text' of undefined
Open
Nobody has claimed this yet.
kind/bug
- 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.4
Stack trace
TypeError: Failed to handle key=s. Cannot read property 'text' of undefined
at Function.putMulticursorRegister (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:1:26285)
at Function.put (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:1:25484)
at C.run (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:1:44034)
at j.run (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:1:51235)
at or.exec (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:1:129295)
at or.execCount (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:1:24066)
at D.runAction (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:11:130026)
at D.handleKeyAsAnAction (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:11:129422)
at D.handleKeyEvent (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:11:126231)
at processTicksAndRejections (internal/process/task_queues.js:94:5)
at async Object.promise (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:9:228221)
at async Object.runTasks (/home/king/.vscode/extensions/vscodevim.vim-1.18.4/out/extension.js:11:285853)
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
The stack trace points to out/extension.js, especially putMulticursorRegister and put; first determine the missing VS Code/Vim actions because the numbered reproduction steps are placeholders. Reproduce the key=s failure, then trace those entry points and verify that the same action no longer raises the reported TypeError.
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
- 25/100