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

Reopen all tabs when opened, in their respective last folder, and maybe with their own history #6032

Closed
softlion opened this issue May 20, 2020 · 4 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

@softlion
Copy link

Description of the new feature/enhancement

After the app has been closed, when the app is reopened, it would be nice if it reopens all tabs, like the chrome browser does.
It could reopen the tabs in their respective last folder, and maybe with their own command history.

The command line app of a Mac already has that great feature.
Which will go in the same direction of "reopening your desktop in the state it was when you closed it" paradigm.

@softlion softlion added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 20, 2020
@ghost ghost added 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 labels May 20, 2020
@rhuijben
Copy link

Would be very nice, but also extermely hard to do. The separation between the terminal and the application that is running inside makes information like the current folder and the history unavailable.

@maciejmiara
Copy link

I think that it'd be great if at least last closed tabs could be opened with respective profiles and panes layout :)

@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #961 for more discussion.

/dup #961

There's also more discussion in #1056, #960, and #766 with related conversations.

@ghost
Copy link

ghost commented May 20, 2020

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 May 20, 2020
@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 May 20, 2020
This issue was closed.
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

4 participants