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.
Post History
I was able to fix this by deleting the ~/.config/VSCode/Workspaces folder. To figure this out, I: Backed up my VSCode folder to /var/tmp Deleted ~/.config/VSCode, after this VS Code stopped ...
Answer
#1: Initial revision
by
matthewsnyderâ€
·
2023-06-16T23:42:27Z (over 1 year ago)
I was able to fix this by deleting the `~/.config/VSCode/Workspaces` folder. ---------- To figure this out, I: * Backed up my `VSCode` folder to `/var/tmp` * Deleted `~/.config/VSCode`, after this VS Code stopped opening two windows (and created a lot of new files in `VSCode/`) * Used `fd` to make a list of all files in `/var/tmp/VSCode` and `~/.config/VSCode/`. * Used `comm` to 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.