VSCodeVim / VSCodeVim/Vim

Failed to handle key `<C-v>`: Cannot read property 'pushUndoStop' of null

Open
#7,568 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.22.2

Stack trace
TypeError: Cannot read property 'pushUndoStop' of null
    at i.applyEdits (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1521:15338)
    at Na.$tryApplyEdits (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2375:18024)
    at u._doInvokeHandler (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1529:13100)
    at u._invokeHandler (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1529:12784)
    at u._receiveRequest (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1529:11446)
    at u._receiveOneMessage (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1529:10124)
    at vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1529:8233
    at f.invoke (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:67:145)
    at c.fire (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:67:1856)
    at l.fire (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:83:19607)
    at m._receiveMessage (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:83:24188)
    at vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:83:21722
    at f.invoke (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:67:145)
    at c.fire (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:67:1856)
    at c.acceptChunk (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:83:16438)
    at vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:83:15568
    at Socket.B (vscode-file://vscode-app/c:/Users/carco/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3069:8467)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)

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 the Ctrl-v failure in VSCodeVim 1.22.2 and review the provided stack trace, which points only to VS Code's bundled workbench code and does not identify a repository file. The issue provides no failing test or defined expected behavior, so the relevant source location and completion criteria must be established before implementation.

Written by the indexing model from the issue text.

Assessment

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