the directory ~/.vscode-oss is created

[daiyam]

Describe the bug

I've tested VSCodium on linux and I found out that it creates the directory ~/.vscode-oss. It shouldn't do that.

Here the tested distros:

• lastest Arch (arch)
• Fedora 33 (rpm)
• Linux Mint 18.3 (deb)
• PoP! OS 20.04 (deb)

[daiyam]

Soon, I will have a PR to fix this issue. Also it isn't limited to linux...
Here it is: #673

[paulcarroty]

Yeah, it's described in docs. So you should fix them too. Maybe add a temporal small note to README for non-breaking user experience.

[daiyam]

Ya, I was doing some testing on Linux and was seeing the directory being created. And I was asking myself, why that vscode-oss is being created since it's VSCodium??? I do think it should be changed.

[stripedpajamas]

It's from the product.json. I figured that people who built manually (Code OSS) would want to share settings/extensions with VSCodium. Maybe should be a fully separate dir. Any particular problem with it using .vscode-oss though?

[paulcarroty]

The problem is lack of clarity. Some users may delete .vscode-oss by mistake like I did 😊

For sharing a symlink is enough, but it feels strange as default.

[paulcarroty]

Any progress here?

[janpb]

Late for the party, but following option can overcome installing extensions in ~/.vscode-oss. However, it doesn't get rid of the directory itself (unfortunately).

You can use the --extensions-dir option to set the install directory for extension, e.g.

code-oss --user-data-dir "$HOME/.config/vscode" --extensions-dir "$HOME/.config/vscode/extensions"'

This create no extension directory in ~/.vscode-oss, which has now only the file argv.json.

Hope this helps

[daiyam]

I think it should be part of #293