"Continue where you left off" behavior #11495

Closed
opened 2026-01-31 02:49:14 +00:00 by claunia · 3 comments
Owner

Originally created by @stagefright5 on GitHub (Nov 19, 2020).

Description of the new feature/enhancement

Behavior somewhat similar to the browser where on start up, the terminal will remember the tabs that were opened.
The things to remember:

  • Type of the tab (cmd, powershell etc)
  • The directory
    ...etc

Proposed technical implementation details (optional)

NA

Originally created by @stagefright5 on GitHub (Nov 19, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Behavior somewhat similar to the browser where on start up, the terminal will remember the tabs that were opened. The things to remember: - Type of the tab (cmd, powershell etc) - The directory ...etc # Proposed technical implementation details (optional) NA <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:49:14 +00:00
Author
Owner

@Don-Vito commented on GitHub (Nov 19, 2020):

This a great and old idea: please review #961 and see if the spec there covers you needs.

I am not from the team, but lately I've seen a lot of work around state persisting, so I guess some parts of this one will be addressed in the future (it seems that retrieving cwd is not trivial, as per discussion in the original ticket)

@Don-Vito commented on GitHub (Nov 19, 2020): This a great and old idea: please review #961 and see if the spec there covers you needs. I am not from the team, but lately I've seen a lot of work around state persisting, so I guess some parts of this one will be addressed in the future (it seems that retrieving cwd is not trivial, as per discussion in the original ticket)
Author
Owner

@DHowett commented on GitHub (Nov 19, 2020):

/dup #961

Thanks @Don-Vito! Appreciate you helping us out with Triage 😄

@DHowett commented on GitHub (Nov 19, 2020): /dup #961 Thanks @Don-Vito! Appreciate you helping us out with Triage :smile:
Author
Owner

@ghost commented on GitHub (Nov 19, 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 commented on GitHub (Nov 19, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11495