VSCodeVim / VSCodeVim/Vim

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

Open
#5,869 2 comments 0 reactions 0 assignees View on GitHub

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:

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

VSCodeVim version: 1.18.5

Stack trace
Error: Failed to handle key=g. Illegal value for `line`
	at d._lineAt (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:571:740)
	at Object.lineAt (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:570:715)
	at le (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:1:206217)
	at n.execActionWithCount (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:1:206753)
	at F.executeMovement (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:175649)
	at F.runAction (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:171527)
	at F.handleKeyAsAnAction (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:170985)
	at F.handleKeyEvent (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:167823)
	at Object.promise (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:9:216277)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async Object.runTasks (/Users/isaacmoovn/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:327644)

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

Start by reproducing key=g with VSCodeVim 1.18.5, then trace the handling path in out/extension.js corresponding to the stack trace. Done means the key no longer produces “Illegal value for line” in the reported scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
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.