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.

Sign up for GitHub

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

Jump to bottom

Terminal should support restart/resume #1252

Closed
bitcrazed opened this issue Jun 13, 2019 · 1 comment
Closed

Terminal should support restart/resume #1252

bitcrazed opened this issue Jun 13, 2019 · 1 comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@bitcrazed
Copy link
Contributor

Summary

Terminal should be restartable:

  • When closed, Terminal should persist it's visual state to a file
  • When opened, if the Terminal state file exists and contains state data, the TErminal should restore its state from the state data, restoring its visual appearance, text content, etc. mirroring its visual state at the point that the Terminal was closed

Notes:

  • This does not mean that terminal tabs/panes should re-attach to the connections they were connected to when the Terminal was closed - this may be impossible in some cases - but the user should be able to see the content within each tab/pane, as it was when the Terminal was closed
  • It may be possible to query the attached shell for environment data, inc. cwd before closing. In which case, Terminal should attempt to cd to the last recorded cwd, restore env-vars, and resume in some cases (e.g. when restoring connection to in-box shells.

When displaying restored content, the text should indicate that it is in read-only state, perhaps by dimming the text's luminance by some visible percentage.

Proposed technical implementation details (optional)
@bitcrazed bitcrazed added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 13, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 13, 2019
@bitcrazed bitcrazed mentioned this issue Jun 13, 2019
Open
@zadjii-msft
Copy link
Member

This is a combo of #766 and #961

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jun 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bitcrazed @zadjii-msft