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

Keep terminal content after reconnecting (SSH) #95183

Closed
jehon opened this issue Apr 14, 2020 · 7 comments
Closed

Keep terminal content after reconnecting (SSH) #95183

jehon opened this issue Apr 14, 2020 · 7 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality remote Remote system operations issues terminal Integrated terminal issues
Milestone

Comments

@jehon
Copy link

jehon commented Apr 14, 2020

Using VSCode insider, we have the great "remote SSH", working on a remote server.

When the connection is lost, VSCode propose to reconnect to the server. Great.
But when it does, we loose all the terminal windows, and more important, all the content of those windows.

I would appreciate if the "content" of the terminal windows would remain, even if the tab is not connected anymore... Something like a "Dead pane"... allowing us to see what did happen in the terminal while reloading the window.

Have a nice day

@Tyriar Tyriar added feature-request Request for new features or functionality terminal Integrated terminal issues remote Remote system operations issues labels Apr 14, 2020
@Tyriar
Copy link
Member

Tyriar commented Apr 14, 2020

Related: #20013

@Tyriar Tyriar added this to the Backlog milestone Apr 14, 2020
@jehon
Copy link
Author

jehon commented Apr 15, 2020

Yes indeed, if 20013 is implemented, this could be solved too...

This one is a bit more simple, in a way that I would like only the content to be kept (ex: to see the result of a long run), and not the connection itself...

@Tyriar
Copy link
Member

Tyriar commented Apr 15, 2020

@jehon keeping the content is actually one of the harder parts, luckily it looks like we've started prioritizing #20013 as a long term goal and it's on this plan with this item:

xterm.js: Prepare client/server separation for terminals xtermjs/xterm.js#2749

#95168

@JavaCS3
Copy link

JavaCS3 commented Apr 26, 2020

xterm-addon-serialize can solve this problem

@jehon
Copy link
Author

jehon commented May 8, 2020

Thinking about this, one acceptable solution for me would be to automatically start a "screen" session when starting the terminal, and to reconnect to it when restarting the vs-code...

@Tyriar
Copy link
Member

Tyriar commented May 8, 2020

I have plans for this such that it should work on Windows, with any shell and not needing outside dependencies. Part of this was even on the iteration plan last month pointing at xtermjs/xterm.js#2749

@Tyriar
Copy link
Member

Tyriar commented Oct 11, 2021

This feature has been implemented, there's an issue with it that may be breaking it though #133741

@Tyriar Tyriar closed this as completed Oct 11, 2021
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 11, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Nov 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality remote Remote system operations issues terminal Integrated terminal issues
Projects
None yet
Development

No branches or pull requests

3 participants