-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to modify product.json #90
Comments
Hey @itspngu, will be great if you make a PR about it! =) |
Just here to say that if I am not mistaken, this is technically illegal. |
Also refer: VSCodium/vscodium#940 (comment) |
@mpauper very curious being a newbie, how is it technically illegal to document this? |
While I think you are kidding even without an explicit smiley: anyone is free to document this, but both using Pylanc and the MS marketplace means you need to follow their license - which explicit says that the license only allows those to be used with Microsoft products (and Microsoft made quite clear that "vscode-oss builds" don't match that description). It would therefore be most reasonable to document that instead of any hacks one should use https://github.com/flathub/com.visualstudio.code if one wants to use these Microsoft services and (binary-only distributed) extensions. |
I just spent about half an hour reading through Github issues and source code of VSCode & VSCodium to figure out how to get Pylance working. In short:
product.json
file, butfind $HOME/.var/app/com.vscodium.codium -name 'product.json'
returns nothingproduct.json
to merge into the compiled-in values - by default, noproduct.json
is included in shipped builds$HOME/.var/app/com.vscodium.codium/config/VSCodium/product.json
lets me run Pylance:As this is a rather specific workaround to a specific problem, perhaps just including a note somewhere is enough to spare others from having to go through the same journey.
The text was updated successfully, but these errors were encountered: