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

Remember my last open tabs (like a browser) + remember my command history #5242

Closed
mbriand1 opened this issue Apr 4, 2020 · 5 comments
Closed

Remember my last open tabs (like a browser) + remember my command history #5242

mbriand1 opened this issue Apr 4, 2020 · 5 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

@mbriand1
Copy link

mbriand1 commented Apr 4, 2020

Description of the new feature/enhancement

My Edge browser can remember my last opened tab, why not the same feature for the terminal? If I open 3 tabs I could have a checkable option in the menu to remember my last tabs. Bonus points for remembering also my command history as I left it...

Productivity gains.

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

j4james commented Apr 4, 2020

I think this is already covered by issue #961.

@oising
Copy link
Collaborator

oising commented Apr 5, 2020 •
edited
Loading

/dup #961

@oising oising closed this as completed Apr 5, 2020
@oising
Copy link
Collaborator

oising commented Apr 5, 2020

Seems the magic dup bot ignores me.

@DHowett-MSFT
Copy link
Contributor

/dup #961

we should iron that out, because it's really helpful having you triage 😄

@ghost
Copy link

ghost commented Apr 5, 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 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 Apr 5, 2020
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
4 participants
@oising @j4james @DHowett-MSFT @mbriand1