Save the terminal's current configuration (tabs, directories, and panes) #11281

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

Originally created by @Yuval91 on GitHub (Nov 4, 2020).

Description of the new feature/enhancement

Proposed technical implementation details (optional)

Originally created by @Yuval91 on GitHub (Nov 4, 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 <!-- Save current configuration of the terminal. with current tabs, their names and colors; current directory and current panes with current directories. This configuration should then be accessed by command palette and/or invoked with a flag and a number (i.e "wt --configuration 1" where "--configuration" could be abbreviated to "-c" and the number could be also a name --> # Proposed technical implementation details (optional) <!-- This could be done manually by the user with the "wt [options] [command]". So, all we need is a script the record the current configuration and generate a relevant "wt" script to be open and saves it as command palette (for example)-->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:43:14 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Nov 4, 2020):

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #766 or #961 for more discussion.

/dup #766
/dup #961

@zadjii-msft commented on GitHub (Nov 4, 2020): Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #766 or #961 for more discussion. /dup #766 /dup #961
Author
Owner

@ghost commented on GitHub (Nov 4, 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 4, 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#11281