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

Feature Request: Remember history #1924

Closed
codemwnci opened this issue Jul 11, 2019 · 1 comment
Closed

Feature Request: Remember history #1924

codemwnci opened this issue Jul 11, 2019 · 1 comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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

@codemwnci
Copy link

Summary of the new feature/enhancement

Following a restart of the terminal app, whether that is within an active session, or after windows restart, it would be useful to pick up where I left off...which would include

  1. The previously opened tabs
  2. The previously buffered outputs
  3. The previously run commands in the command history

Basically, try to make it behave more like a multi-tab browser would behave.

@codemwnci codemwnci added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 11, 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 Jul 11, 2019
@zadjii-msft
Copy link
Member

This is mostly a dupe of #961.

Unfortunately, restoring the command history is something the shell (cmd.exe, powershell, bash) would be responsible for. Powershell and bash both already persist command history, but cmd.exe doers not. Unfortunately, we'll never be able to change that about cmd.exe either, as it's a parked codebase.

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jul 11, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 11, 2019
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. 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
Development

No branches or pull requests

2 participants