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

Opening multiple tabs from a single profile on start, with the default terminal, and on individual profiles. #4229

New Issue
Closed
opened 2026-01-30 23:41:30 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:41:30 +00:00
Owner
Copy Link

Originally created by @danielkeery on GitHub (Oct 3, 2019).

Description of the new feature/enhancement

This FR would solve having to manually setup my workspace on every new launch. I always start with the same 3 tabs, it would be nice to launch these all in the default.

"globals": {
"defaultProfile": ["GUID1", "GUID2", "MULTI-PROFILE-GUID1", ...]
}
...
"profiles": [
{
"guid": "multi-profile guid",
"launchProfiles": ["other profile guid1", "other profile guid 2", ...]
}
]

Proposed technical implementation details (optional)

Change existing launch code into a for loop and the defaultProfile backing as a array.
Either new profile type could be introduced or the detection of launchProfiles for each profile configuration would signal needing to launch other profiles. Recursive?
Support the launching of multiple profiles in any launch action. Should be self explanitory.

Originally created by @danielkeery on GitHub (Oct 3, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 This FR would solve having to manually setup my workspace on every new launch. I always start with the same 3 tabs, it would be nice to launch these all in the default. "globals": { "defaultProfile": ["GUID1", "GUID2", "MULTI-PROFILE-GUID1", ...] } ... "profiles": [ { "guid": "multi-profile guid", "launchProfiles": ["other profile guid1", "other profile guid 2", ...] } ] # Proposed technical implementation details (optional) Change existing launch code into a for loop and the defaultProfile backing as a array. Either new profile type could be introduced or the detection of launchProfiles for each profile configuration would signal needing to launch other profiles. Recursive? Support the launching of multiple profiles in any launch action. Should be self explanitory.
claunia commented 2026-01-30 23:41:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 3, 2019):

So I suppose this was discussed before in #1043, though there doesn't seem like there's a unique issue for it, so congratulations, this is now the thread :)

There are probably a bunch of things we'd want to consider as part of a comprehensive solution here.

  • What if someone wants to open the terminal with multiple tabs (what you've already discussed above)
  • What about with multiple panes, in various different split configurations? How would we set that?
  • Perhaps the user wants to auto-launch multiple windows? In different locations, etc.
  • Obviously, any solution for the above three should not preclude any of the others. Users would want to be able to specify multiple windows, each with their own tabs, and with tabs that might have any number of panes.
  • Would we want this multi-launch behavior to only happen on first launch, or every Terminal launch?
  • With the nesting behavior you have above, what if someone had a recursive loop, where one profile A specified launching profile B, and B specified launching A? That would theoretically cause an infinite loop - do we allow that?
  • (I'm sure there's more I'm missing here)

This is certainly a problem that's feasible from an engineering standpoint, but due to the complexity of specifying these scenarios, I'd want a spec written first to try and think through the edge cases before we start working on the code.

@zadjii-msft commented on GitHub (Oct 3, 2019): So I suppose this was discussed before in #1043, though there doesn't seem like there's a unique issue for it, so congratulations, this is now the thread :) There are probably a bunch of things we'd want to consider as part of a comprehensive solution here. * What if someone wants to open the terminal with multiple tabs (what you've already discussed above) * What about with multiple panes, in various different split configurations? How would we set that? * Perhaps the user wants to auto-launch multiple _windows_? In different locations, etc. * Obviously, any solution for the above three should not preclude any of the others. Users would want to be able to specify multiple windows, each with their own tabs, and with tabs that might have any number of panes. * Would we want this multi-launch behavior to only happen on _first_ launch, or _every_ Terminal launch? * With the nesting behavior you have above, what if someone had a recursive loop, where one profile A specified launching profile B, and B specified launching A? That would theoretically cause an infinite loop - do we allow that? * (I'm sure there's more I'm missing here) This is certainly a problem that's feasible from an engineering standpoint, but due to the complexity of specifying these scenarios, I'd want a [spec](https://github.com/microsoft/terminal/blob/master/doc/specs/spec-template.md) written first to try and think through the edge cases before we start working on the code.
claunia commented 2026-01-30 23:41:31 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 8, 2019):

I'm actually gonna merge this one back into /dup #756, since I found the original "multiple tabs on startup (and more)" issue.

@DHowett-MSFT commented on GitHub (Oct 8, 2019): I'm actually gonna merge this one back into /dup #756, since I found the original "multiple tabs on startup (and more)" issue.
claunia commented 2026-01-30 23:41:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 8, 2019):

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 (Oct 8, 2019): 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.
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 Area-Settings Help Wanted Issue-Feature Product-Terminal 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#4229
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?