Failed to handle key=<C-h>. Cannot read property 'match' of undefined
Open
Nobody has claimed this yet.
status/needs-more-info
- 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.17.2
Stack trace
TypeError: Failed to handle key=<C-h>. Cannot read property 'match' of undefined
at Function.immediateMatchingBracket (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:94241)
at c (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:481980)
at c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:482860
at t.ExtHostTextEditor.edit (c:\Users\dr_d00m4n\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:651:588)
at F.executeCommand (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:482834)
at F.runAction (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:475478)
at processTicksAndRejections (internal/process/task_queues.js:94:5)
at async F.handleKeyAsAnAction (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:474794)
at async F.handleKeyEvent (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:471603)
at async Object.promise (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:231560)
at async Object.runTasks (c:\Users\dr_d00m4n\.vscode\extensions\vscodevim.vim-1.17.2\out\extension.js:9:621914)
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 C-h key handling failure in VSCodeVim 1.17.2, then inspect the immediateMatchingBracket stack frame in out/extension.js. Trace that entry point back to its TypeScript source and determine the input that is undefined. Done means the reproduction no longer raises the reported TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vim, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100