Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
How to prevent Visual Studio Code from opening an extra blank window?
When I run code . in a directory, Visual Studio Code opens two windows. The first is empty, the second shows directory I was in as expected.
I checked ~/.config/VSCode/Workspaces and there is only one in there for a different folder, so that can't be it.
I found a bug about this https://github.com/microsoft/vscode/issues/128175 but that's apparently fixed in 2021, so that wouldn't be it either. My VSC version was 1.77.3 - after updating to 1.79.0 the issue persists.
How can I figure out why VS Code is opening two windows and stop it?
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
The following users marked this post as Works for me:
| User | Comment | Date |
|---|---|---|
| matthewsnyder | (no comment) | Jun 16, 2023 at 23:42 |
I was able to fix this by deleting the ~/.config/VSCode/Workspaces folder.
To figure this out, I:
- Backed up my
VSCodefolder to/var/tmp - Deleted
~/.config/VSCode, after this VS Code stopped opening two windows (and created a lot of new files inVSCode/) - Used
fdto make a list of all files in/var/tmp/VSCodeand~/.config/VSCode/. - Used
commto print only filenames unique to the first one.
A lot of these were cache paths, so I decided to start deleting them one by one to see what would fix the issue. As luck would have it, the first one I tried was Workspaces, which did fix it.
My Workspaces contained a single JSON, which had two elements in the folders key. Deleting these didn't seem to help, but deleting the file did.
0 comment threads
I've not seen the problem myself, but I did find a mention of the "workbench.editor.enablePreview" setting possibly influencing this. Can you try setting this to false, and see if it makes a difference?
1 comment thread
1 comment thread