VSCodeVim / VSCodeVim/Vim

continuously changing settings.json

Open
#9,768 2 comments 1 reaction 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:

It seems the extension write my user setting file every operation

Image

To Reproduce
Steps to reproduce the behavior:

  1. reproduce the settings (maybe needed)
  • "vim.vimrc.enable": false,
  • "vim.vimrc.path": "...", (currently an invalid path)
  • "vim.statusBarColorControl": true, (maybe not needed)
  • "vim.xxxKeyBindings": ... (maybe not needed)
  1. open a random folder and open a random file
  2. some vim operations, like:
  • change to normal mode by ""
  • append a new line by "o"
  1. if you open the output panel, and change to vim output, you'll find vim changes your settings.json every single operation

Screenshots
attached above

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 1.30.1
  • VSCode version: 1.104.2
  • OS: macOS 15.6.1 M3

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

No source file or test is named. Reproduce with the listed vim settings, open a random folder and file, perform the described operations, and inspect the Vim output panel to identify why settings.json is written each time; done when ordinary Vim operations no longer cause repeated settings writes.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.