Failed to handle key=s. Cannot read property 'text' 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=s. Cannot read property 'text' of undefined
at Function.putMulticursorRegister (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:734854)
at Function.put (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:734053)
at C.run (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:521745)
at N.run (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:528946)
at or.exec (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:415825)
at or.execCount (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:355716)
at F.runAction (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:707796)
at F.handleKeyAsAnAction (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:707190)
at F.handleKeyEvent (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:704026)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async Object.promise (c:\Users\Pedro Quispe\.vscode\extensions\vscodevim.vim-1.18.9\out\extension.js:2:350696)
at async Object.runTasks (c:\Users\Pedro Quispe\.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 with the reported stack trace in out/extension.js, focusing on the putMulticursorRegister and put entry points. Reproduce the failure with key=s and gather the missing steps or context needed to identify the triggering command; done means the error no longer occurs in that scenario and the behavior is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100