-
Notifications
You must be signed in to change notification settings - Fork 57
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
Support VS Codium #14
Comments
Just an unofficial FYI for anyone wanting to use this without using VS Code / using vscodium and not wanting to deal with building. Quick hack to make this work on vscodium on the provided bins and extensions:
grep -rl vscode . | LC_ALL=C xargs sed -i "" 's/vscode/vscodium/g'
Should be able to establish comms and be operational. Would need to do this with every upgrade, so just a hack / fyi. For the devs: looks like everything works with this simple mod, so maybe just adding a vscode || vscodium || vscodeoss or chain everywhere a vscode literal exists would make this work. In the extension, just need to check the extension bin dir and if it's in vscode-oss, then it's using vscodium. I'm sure there is a better way in the API to detect that, and in the IPC source just change it from "vscode" as the app name to an if - else statement setting it based on the app. Should be a pretty straight-forward change; I'll maybe do that when I have more time and submit a pull request. |
I'd be supportive of the change above—generalizing |
A faster solution: rename (or duplicate*) |
Context
Please support VS Codium.
I do not want to be tracked by Microsoft so I use VS Codium. It is an OSS fork of VS Code that has all the same features, minus telemetry. It should work with minor code changes as it has all the same considerations as vs code. I installed the VS Code plugin to VS Codium but it does not seem to work. There are too many places that have hardcoded settings for VS Code for me to manage manually going through.
Goals
I want to use this with VS Codium instead of VS Code.
Proposed Solution
Make the VS Code editor configurable to support whatever version is installed
Alternatives
There is no downside to doing this.
The text was updated successfully, but these errors were encountered: