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

[supervisor] Support spawning Gitpod tasks as tmux windows #14988

Closed
axonasif opened this issue Nov 28, 2022 · 5 comments
Closed

[supervisor] Support spawning Gitpod tasks as tmux windows #14988

axonasif opened this issue Nov 28, 2022 · 5 comments

Comments

@axonasif
Copy link
Member

axonasif commented Nov 28, 2022

Is your feature request related to a problem? Please describe

Tmux integration would allow for easy interactivity with Gitpod tasks on SSH and give a more 'first-class' feel to neo(vim)/emacs/ssh users in general.

Describe the behaviour you'd like

  • A option in preferences for enabling tmux integration.
  • supervisor then opens all Gitpod tasks inside a tmux session as windows.
  • (proposal): Auto-install gitpod.tmux plugin when the integration is enabled by executing the plugin from /etc/tmux.conf. (to provide a similar experience as the Gitpod VSCode theme/integrations)
  • Since all tasks would be opened in tmux, set tmux as the default shell in Machine settings.json of vscode with the following: here

Describe alternatives you've considered

Additional context

Internal slack thread.

@akosyakov
Copy link
Member

I think we should think how we make IDEs pluggable integrations not built in in supervisor as a general solution.

@axonasif
Copy link
Member Author

That would be great as well.

@axonasif
Copy link
Member Author

BTW, one of the other reasons for suggesting to implement this to supervisor was to also use it for #7671 implementation where you'd pass on /.supervisor into the testing container and launch the Gitpod tasks in tmux for easy debugging. But it's just a proposal 🙂

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

1 similar comment
@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
Projects
None yet
Development

No branches or pull requests

2 participants