starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Suggestion: Open a new terminal window with a collection of preconfigured tabs #12346

New Issue
Open
opened 2026-01-31 03:13:03 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 03:13:03 +00:00
Owner
Copy Link

Originally created by @NeilMacMullen on GitHub (Feb 1, 2021).

Motivation:

If I perform a common task involving multiple tabs, I usually spend some time to color and name the tabs to make it it obvious which tab is which. For example.

colortabs

It would be convenient if I could store this particular configuration the next day and recall it.

From a user-perspective something like:--

  • Click on shell menu drop-down.
  • Select "Save Collection"
    • Configuration is saved to some config file

Next day...

  • Double click on configuration file
  • new Shell window opens with saved tabs

At a minimum the "collection/configuration" should recreate the number and types of tabs + header colors and names. It would be desirable if additional context for each tab could be maintained (cwd, buffer history, other?)

I'm pretty sure I can do most of this stuff already by writing some dedicated scripts - maybe a cheap implementation of this would be for the "config file" just to be a script that performs the required operations when the shell starts up?

Originally created by @NeilMacMullen on GitHub (Feb 1, 2021). Motivation: If I perform a common task involving multiple tabs, I usually spend some time to color and name the tabs to make it it obvious which tab is which. For example. ![colortabs](https://user-images.githubusercontent.com/9131337/106469408-234cb100-6497-11eb-9a65-0450ec816ba8.png) It would be *convenient* if I could store this particular configuration the next day and recall it. From a user-perspective something like:-- - Click on shell menu drop-down. - Select "Save Collection" - Configuration is saved to some config file Next day... - Double click on configuration file - new Shell window opens with saved tabs At a minimum the "collection/configuration" should recreate the number and types of tabs + header colors and names. It would be *desirable* if additional context for each tab could be maintained (cwd, buffer history, other?) I'm pretty sure I can do most of this stuff already by writing some dedicated scripts - maybe a cheap implementation of this would be for the "config file" just to be a script that performs the required operations when the shell starts up?
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:13:03 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12346
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?