Failed to handle key=<C-a>. Unexpected mode in IncrementDecrementNumberAction.getPositions()
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.20.0
Stack trace
Error: Failed to handle key=<C-a>. Unexpected mode in IncrementDecrementNumberAction.getPositions()
at zt.getSearchRanges (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\actions\commands\actions.ts:2942:15)
at zt.exec (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\actions\commands\actions.ts:2794:25)
at zt.execCount (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\actions\base.ts:249:20)
at b.exec (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\actions\commands\insert.ts:145:22)
at runMicrotasks (<anonymous>)
at process.j (internal/process/task_queues.js:97:5)
at b.execCount (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\actions\base.ts:248:42)
at I.actionToRecord [as runAction] (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\mode\modeHandler.ts:722:40)
at I.handledAsAction [as handleKeyAsAnAction] (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\mode\modeHandler.ts:651:43)
at I.async [as handleKeyEvent] (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\mode\modeHandler.ts:471:11)
at Object.promise (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\extensionBase.ts:628:27)
at Object.runTasks (c:\Users\navee\.vscode\extensions\vscodevim.vim-1.20.0\src\taskQueue.ts:36:26)
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 src/actions/commands/actions.ts around the getSearchRanges and exec locations in the stack trace, then follow the call from src/actions/commands/insert.ts. Reproduce the failure in VSCodeVim 1.20.0 and trace the mode handling that reaches IncrementDecrementNumberAction.getPositions(). Done means the key no longer raises the reported unexpected-mode 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
- 35/100