VSCodium start-up error: No module named jedi_language_server microsoft/vscode-python#22176 Closed Collaborator filiptronicek commented Oct 13, 2023 Hello there @mammo0 👋. We have now republished the affected version of the Python extension. Could you try if it works for you now? 👍...
OpenVSCodeServer is similar to VSCodium in that is also not allowed to connect to Microsoft Visual Studio Code Marketplace and suffers from the same ecosystem fracture by design problem. The project is a company-driven, freely-licensedserver distributionof Visual Studio Code in binary form that i...
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)
Up to now, not bad, I can run the jar package (java -jar my_project) that I get from that just from the terminal. Still, since I know that it is a Maven project, else the build/compile with Maven would not work, I want to set up the project as a Maven project i...
VSCode seems to completely ignore this option and falls back to OS detection. VSCodium does not do this. I checked the chromium source (https://source.chromium.org/chromium/chromium/src/+/main:components/os_crypt/sync/key_storage_util_linux.cc;drc=4944da41dfc9b2d58f42ce6669c4abec978c7319...