Skip to content

SSH as the default editor #17928

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

Closed
daniloraisi opened this issue Jun 13, 2023 · 10 comments
Closed

SSH as the default editor #17928

daniloraisi opened this issue Jun 13, 2023 · 10 comments
Labels

Comments

@daniloraisi
Copy link

Is your feature request related to a problem? Please describe

This is a feature request.

Describe the behaviour you'd like

Allow the user to select SSH as the default editor when creating a new Workspace

image

@loujaybee
Copy link
Member

Thanks @daniloraisi ! Can I ask a couple questions on your context....

  1. What is the experience you're expecting when you set SSH as the default editor? An easier way to copy paste the SSH connection string for your local machine? Or something else?
  2. What do you then do with the copied SSH string? Are you pasting that into another application to connect, or using it for direct editing? How many connections do you typical open, and for what?
  3. Do you currently have a public key uploaded to gitpod? or are you using the access token SSH connection string?
  4. We have early support for a browser based terminal (https://github.com/gitpod-io/website/pull/3684) would that be something you'd be interested to try out? (it's currently in private beta)

@loujaybee
Copy link
Member

I think this also could be a duplicate of this issue:

@daniloraisi
Copy link
Author

Thanks for the quick replay @loujaybee

  1. What is the experience you're expecting when you set SSH as the default editor? An easier way to copy paste the SSH connection string for your local machine? Or something else?

My original thought was the ability to copy the SSH connection string without clicking the button More Actions... and then Connect via SSH.

  1. What do you then do with the copied SSH string? Are you pasting that into another application to connect, or using it for direct editing? How many connections do you typical open, and for what?

I use my local terminal to connect—usually, only one connection. I have dotfiles configuring my GitPod to have TMUX and all the tools I need from a single SSH connection.

  1. Do you currently have a public key uploaded to gitpod? or are you using the access token SSH connection string?

Yes, I connect with a public/private key instead of an Access token.

  1. We have early support for a browser based terminal (Document the Browser Terminal website#3684) would that be something you'd be interested to try out? (it's currently in private beta)

I'm interested in testing if possible.

@daniloraisi
Copy link
Author

I think this also could be a duplicate of this issue:

I see this as a possibility, but not related to my request. I use Neovim when connected to GitPot through SSH, but I have dotfiles to configure it.

My idea was to provide a simple way to copy the SSH connection string or, in a different approach, as you presented in https://github.com/gitpod-io/website/pull/3684.

@daniloraisi
Copy link
Author

@akosyakov @loujaybee, any chance to get early access to the In-Browser SSH to help testing?

@akosyakov
Copy link
Member

@filiptronicek you can whitelist by user id?

@loujaybee
Copy link
Member

Hey @daniloraisi we are adding you now, can you check if you see it in the dropdown of editors? 🙏

If you have any feedback, we'd love to hear it.

@daniloraisi
Copy link
Author

Hello @loujaybee, I saw the option and started using it.
I'm using TMUX with some specific configurations. I faced a strange situation. Where can I send all the info regarding this?

@loujaybee
Copy link
Member

Here is good, but any option in: https://gitpod.io/support also works.

Feel free to tag me on Discord, also! https://gitpod.io/chat too 🙏

@stale
Copy link

stale bot commented Sep 16, 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 16, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants