VSCodeVim / VSCodeVim/Vim

Failed to handle key=c. Illegal value for `line`

Open
#6,152 0 comments 0 reactions 0 assignees View on GitHub

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:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

VSCodeVim version: 1.18.9

Stack trace
Error: Failed to handle key=c. Illegal value for `line`
	at v._lineAt (/private/var/folders/qs/3jmn2_r553z8bqchp2kdsl6w0000gn/T/AppTranslocation/155C7C0C-4784-4AF0-9040-D28A25B5B910/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:81:1166)
	at Object.lineAt (/private/var/folders/qs/3jmn2_r553z8bqchp2kdsl6w0000gn/T/AppTranslocation/155C7C0C-4784-4AF0-9040-D28A25B5B910/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:81:95)
	at C.run (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:521665)
	at N.run (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:528946)
	at F.executeOperator (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:713529)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:97:5)
	at async F.runAction (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:708540)
	at async F.handleKeyAsAnAction (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:707179)
	at async F.handleKeyEvent (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:704015)
	at async Object.promise (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:350696)
	at async Object.runTasks (/Users/jay/.vscode/extensions/vscodevim.vim-1.18.9/out/extension.js:2:754577)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure by pressing key=c in VSCodeVim 1.18.9, then trace the error through out/extension.js, especially the run and executeOperator entries shown in the stack trace. Done means the key no longer raises the illegal line error; no test file is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.