VSCodeVim / VSCodeVim/Vim

globalStorage/vscodevim.vim/.registers': Error: ENOENT: no such file or directory

Open
#8,072 2 comments 2 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

Describe the bug

After installing VSCodeVim, the output shows this error:

[2022-10-31 17:25:47.625] [renderer1] [error] ENOENT: no such file or directory, open '/home/user/.config/Code/User/globalStorage/vscodevim.vim/.registers': Error: ENOENT: no such file or directory, open '/home/user/.config/Code/User/globalStorage/vscodevim.vim/.registers'

I've tried re-installing, cleaning things, etc, but the error always comes back.

To Reproduce
Steps to reproduce the behavior:

  1. Install VSCodeVim
  2. Close/Open VSCode
  3. View the "Output" pane
  4. See error

Expected behavior
No error

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 1.24.2
  • VSCode version: 1.72.2
  • OS: Fedora

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 error after installing VSCodeVim 1.24.2, reopening VSCode, and checking the Output pane. Trace handling of the globalStorage/vscodevim.vim/.registers path; done means reopening VSCode no longer reports the ENOENT error on the listed Fedora and VSCode versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.