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

Save/Load - Import/Export state of terminal #11986

Closed
maifeeulasad opened this issue Dec 17, 2021 · 3 comments
Closed

Save/Load - Import/Export state of terminal #11986

maifeeulasad opened this issue Dec 17, 2021 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@maifeeulasad
Copy link

Description of the new feature/enhancement

  • Able to save the current state of the terminal, restart doesn't require creating all those tabs with all those details.
  • Able to export state as JSON or some format, import them whenever wanted

Proposed technical implementation details (optional)
@maifeeulasad maifeeulasad added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Dec 17, 2021
@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 Dec 17, 2021
@j4james
Copy link
Collaborator

j4james commented Dec 17, 2021

Restoring the state (at least the open tabs and panes) should already be supported in preview version 1.12:
https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-12-release/#window-restoration

For other state-related features that are still in development, see issue #9800.

@zadjii-msft
Copy link
Member

Yea, I'm gonna call this /dup #9800, thanks!

@ghost
Copy link

ghost commented Dec 18, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Dec 18, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Dec 18, 2021
This issue was closed.
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. 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
3 participants
@j4james @zadjii-msft @maifeeulasad