-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
VSCodium support #10667
Comments
This extension seems to do the thing (ssh extension replica, but OSS).
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
👀 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
activity |
Wouldn't it be enough to add "VSCodium (Desktop)" to the options that can be chosen, then do the exact same thing as with "VSCode (Desktop)" but instead of using a |
@GitMensch I think the issue is not about establishing a SSH connection, that's already doable (manually), it's about detecting user interaction as heartbeat so that the workspace doesn't timeout. |
It would be nice to not need to start that manually - is there a way I can get GitPod Workspaces to start with a vscodium URL instead (or at least get the vscode URL to clipboard for testing so I can manually change that to the other scheme)? What part does the heartbeat on the "VSCode Desktop" option? The GitPod extension / an internal SSH connection / something else? |
All that's needed to support it should be respecting vscodium's protocol (because it has a different name) but I might be wrong. Just commenting. Edit: whoops looks like someone else said that before me mb |
You should be able to connect using vscodium now, steps:
|
@jeanp413 Thanks for the info. I could not connect by following the instructions you posted. Will this work if I have vscode installed or it is best to remove vscode and follow the steps for codium? I saw that an access token was provided but it is not possible to add the token because the 'token option' for Gitpod is only available for private beta users. |
yes, it should be fine to have both vscode and vscodium installed
@ENate Could you give more info about what step you failed to complete successfully? maybe share gitpod and/or remote-ssh extension logs |
@jeanp413 connecting from vscodium works fine now, can you have a look at letting vscodium be opened by GitPod online, too?
So a request to have an "Gitpod: Open in VSCodium" entry or at least a "Gitpod: Open vscode connection URL"? |
Is your feature request related to a problem? Please describe
I am not a big fan of binaries that microsoft redistributes, they contain some crap I don't really want like telemetry which makes it nonfree software. VSCodium is a good approach to fix it. It builds open source binary without microsoft stuff and uses open source extension store.
However, gitpod "open in vscode" does not open workspace in VSCodium, simply nothing happens.
So here is my suggestion, open workspace in VSCodium
Describe alternatives you've considered
I tried ssh but it wasn't as smooth and easy.
The text was updated successfully, but these errors were encountered: