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

Terminal session history #16569

Closed
Soneji opened this issue Jan 18, 2024 · 3 comments
Closed

Terminal session history #16569

Soneji opened this issue Jan 18, 2024 · 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

@Soneji
Copy link

Soneji commented Jan 18, 2024

Description of the new feature/enhancement

As we all know, in windows, you have to restart often. When I restart my system, all my terminal panes and layout is maintained, however the content in those panes is lost.

I am proposing a feature in windows terminal to maintain this terminal history, as a bonus the session state could also be saved, e.g. the path in which the shell is currently in.

The retention of the terminal history can help me restore each pane to the correct place and easily pick up where I left off.

Is it worth noting I am using WSL 2, I am not sure if some of these features already exist with powershell.

Proposed technical implementation details (optional)

I guess there are two ways this could be implemented

  1. Save the terminal history and shell session to a temp file on shutdown
  2. Periodically save the terminal history and shell session to a temp file on the system
@Soneji Soneji added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 18, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot 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 Jan 18, 2024
@j4james
Copy link
Collaborator

j4james commented Jan 18, 2024

If by history you mean the buffer contents/scrollback, that feature request is tracked in issue #961.

As for saving the current directory, that should already be possible if you've configured your shell appropriately (there's a tutorial here).

@zadjii-msft
Copy link
Member

Yep, that's correct. There's also the firstWindowPreference setting, to enable bringing your windows back to the right position, with the same tabs & panes. Of course, you'll also want to do the aforementioned shell integration, to let Terminal know about the CWD.

image

/dup #961 for the rest of "restore the buffer contents"

Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

3 participants