Skip to content
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

Open
KaspianDev opened this issue Jun 14, 2022 · 15 comments
Open

VSCodium support #10667

KaspianDev opened this issue Jun 14, 2022 · 15 comments
Labels
meta: never-stale This issue can never become stale team: IDE type: feature request New feature or request

Comments

@KaspianDev
Copy link

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.

@axonasif axonasif added type: feature request New feature or request team: IDE labels Jun 15, 2022
@KaspianDev
Copy link
Author

This extension seems to do the thing (ssh extension replica, but OSS).

@stale
Copy link

stale bot commented Oct 16, 2022

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.

@wvffle
Copy link

wvffle commented Nov 27, 2022

👀

@stale
Copy link

stale bot commented Mar 18, 2023

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.

@axonasif
Copy link
Member

Not stale.

@stale
Copy link

stale bot commented Sep 17, 2023

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 17, 2023
@astrojuanlu
Copy link

activity

@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Sep 17, 2023
@akosyakov akosyakov added the meta: never-stale This issue can never become stale label Sep 19, 2023
@GitMensch
Copy link

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 vscode:// url use vscodium://, as per VSCodium/vscodium#1126 (comment)?

@axonasif
Copy link
Member

@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.

@GitMensch
Copy link

GitMensch commented Sep 21, 2023

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?

@KaspianDev
Copy link
Author

KaspianDev commented Sep 21, 2023

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

@jeanp413
Copy link
Member

You should be able to connect using vscodium now, steps:

@ENate
Copy link

ENate commented Nov 15, 2023

@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.

@jeanp413
Copy link
Member

Will this work if I have vscode installed or it is best to remove vscode and follow the steps for codium?

yes, it should be fine to have both vscode and vscodium installed

I could not connect by following the instructions you posted.

@ENate Could you give more info about what step you failed to complete successfully? maybe share gitpod and/or remote-ssh extension logs

@GitMensch
Copy link

GitMensch commented Jan 10, 2024

@jeanp413 connecting from vscodium works fine now, can you have a look at letting vscodium be opened by GitPod online, too?

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)?

So a request to have an "Gitpod: Open in VSCodium" entry or at least a "Gitpod: Open vscode connection URL"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale team: IDE type: feature request New feature or request
Projects
None yet
Development

No branches or pull requests

8 participants