VSCode open by itself new editor with settings.json - visual-studio-code

I don't know what happen, but I was working on VSCODE in windows adding neovim path to the settings.json.
I clicked inside the settings.json and vscode started to open new editor tabs by itself with the same content of settings.json.
I have uninstalled vscode several times, removed the Appdata roaming vscode, the Appdata local code, etc. I installed the vscode again and same behavior. I restarted my windows machine and same behavior.
The sync is on so the settings replicates to all my vscode installations. I started my Linux machine to see if this was something that replicated to my linux version. No, it is working normal.
I can work on VScode if I don't open the settings. It has open new editors (clones of settings) upto 500 hundred times.
I was able to stop it when I changed directory and it asked me if I wanted to close and all open tabs. The moment that I go to settings starts again.

You could start to not sync extentions. Maybe one is breaking it.
But You could also try to install an older version of vs code.
How to downgrade vscode

Related

Settings sync -- settings.json is different between WSL and Windows on same machine yet same file gets synced

Following the method provided in the official documentation here, I turned on sync for [Keyboard Shortcuts] keybindings.json, [User Snippets] cpp.json and [Settings] settings.json.
While VSCode Windows and VSCode on WSL on the same machine share the common keybindings.json and cpp.json files, WSL and Windows do not share the same settings.json file. The Windows version resides as:
C:\Users\Tryer\AppData\Roaming\Code\User\settings.json
and the WSL version resides as
\\wsl$\Ubuntu-20.04\home\Tryer\.vscode-server\data\Machine\settings.json.
These are two different files. When I open code . from within WSL, and issue command Settings Sync: Show Synced Data, clicking on the settings.json file picks up the Windows version C:\Users\Tryer\AppData\Roaming\Code\User\settings.json.
How does one resolve this conflict surrounding which settings.json file is synced on the same machine that runs both Windows and WSL?

Everytime I try to change the default version of my terminal, VSCode opens up instead

When i am trying to change the default terminal on my windows 11 laptop, the terminal opens up VSCode for some reason. I open the windows terminal, hit settings then VSCode opens up with this settings.json page:
VSCode settings.json
But the thing is I want to have the terminal settings open up, not VSCode. I am trying to change my default terminal from windows terminal to Ubuntu.
What version of Windows Terminal are you using? The settings UI for the Terminal was added in 1.7 (IIRC), and I believe the version that originally shipped with Windows 11 was 1.6. Before 1.7, clicking on "settings" would open the settings.json file in whatever your default .json editor was.
Future readers: If you're hitting this too, make sure to update your Terminal from the Store. Anything >=1.7 should have the Settings UI. At the time of this post, the latest Stable version in the store was 1.12.

How to troubleshoot a VSCode extension not loading after restart?

I installed and configured the Apollo GraphQL extension in VSCode. It worked perfectly.
However, when I close and reopen VSCode it doesn't load. The icon never shows up and nothing loads in the console output.
The extension is definitely loaded because syntax highlighting still works but we get none of scheme features.
I tried
uninstall/reinstall of the extension.
closing vscode, deleting the extension folder directly, reinstall extension, restart vscode.
installing the Insiders Edition of vscode and installing the extension there.
In all cases it works the first time but not after a restart.
How can I troubleshoot/fix this issue?

Visual Studio Code remembering old/wrong open editors?

Previous searches for Visual Studio Code show responses for not remembering any open editors, or the opposite, but I seem to be having a novel problem. Within the same workspace, closing VSC and reopening (e.g. after a restart) will reopen some editor windows but they are often files that I had worked in and closed in the past, not the files I had open when VSC was shut down. The Restore Windows setting is set to all. Limit: Enabled for the amount of editors allowed to be open is not checked. Autosave is enabled.
Do I need to be manually saving my workspace? Is there some other obvious setting I'm missing?

VScode caching Issue? File not showing newest changes

I've never seen this before so thought I'd ask here. My vscode isn't showing the latest changes in a file. When I open said file with vim, the file is up-to-date as expected. If I open that same file in vscode, it shows something else.
I've tried restarting vscode, using the 'Clear Editor History' command to clear the editor cache... I've restarted my machine. Nothing seems to work. Any thoughts?