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

Feature Request: Pop out Tabs and List Tabs on Taskbar #18334

New Issue
Closed
opened 2026-01-31 06:10:42 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:10:42 +00:00
Owner
Copy Link

Originally created by @coconut2015 on GitHub (Aug 29, 2022).

The complete idea is the following.

  1. Allow tabs to be popped out into separate WT windows and allows the tabs to be drag-n-dropped much like Edge browser tabs. This allows tabs to be more easily organized. For instance, I could have multiple consoles connecting to a docker instance, and a separate set of consoles connecting to a different docker instance.
  2. List the tabs in the taskbar vertical list when the user left-click the Windows Terminal icon on taskbar. The title of the tab is listed as well along with possible notification (visual BEL). Then the user can select the tab based on the title and notification.
  3. Allow script to launch cmd.exe in named WT window, much like Window.name for setting hyperlink target.

Take this frequent use-case scenario. Usually, I have 10+ command line tabs open investigating multiple issues. I could run a build script in one tab that could take 5-10 minutes, and then run another test script that could take 25 minutes in a different tab, and so on. Many of my scripts have BEL notification generated at the end of the script to indicate that it is done. Then after a coffee break / 1-hr meeting, I would check the tabs with visual BEL to see which tasks have been completed and needs to be inspected etc.

Right now, as a workaround, I am basically running multiple WT windows, each with a single cmd.exe tab running. I am not running cmd.exe by itself since it does not support visual BEL. WT has visual BEL, but it lacks a good way of listing tabs when there are a lot of tabs. However, this workaround defeats the purpose of tab support in WT.

Originally created by @coconut2015 on GitHub (Aug 29, 2022). The complete idea is the following. 1. Allow tabs to be popped out into separate WT windows and allows the tabs to be drag-n-dropped much like Edge browser tabs. This allows tabs to be more easily organized. For instance, I could have multiple consoles connecting to a docker instance, and a separate set of consoles connecting to a different docker instance. 2. List the tabs in the taskbar vertical list when the user left-click the Windows Terminal icon on taskbar. The title of the tab is listed as well along with possible notification (visual BEL). Then the user can select the tab based on the title and notification. 3. Allow script to launch cmd.exe in named WT window, much like Window.name for setting hyperlink target. Take this frequent use-case scenario. Usually, I have 10+ command line tabs open investigating multiple issues. I could run a build script in one tab that could take 5-10 minutes, and then run another test script that could take 25 minutes in a different tab, and so on. Many of my scripts have BEL notification generated at the end of the script to indicate that it is done. Then after a coffee break / 1-hr meeting, I would check the tabs with visual BEL to see which tasks have been completed and needs to be inspected etc. Right now, as a workaround, I am basically running multiple WT windows, each with a single cmd.exe tab running. I am not running cmd.exe by itself since it does not support visual BEL. WT has visual BEL, but it lacks a good way of listing tabs when there are a lot of tabs. However, this workaround defeats the purpose of tab support in WT.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 06:10:42 +00:00
claunia commented 2026-01-31 06:10:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 30, 2022):

@zadjii-msft commented on GitHub (Aug 30, 2022): * /dup #1256 * /dup #687 * /dup #4472 - this you can do today with window names and `wt -w`.
claunia commented 2026-01-31 06:10:44 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 30, 2022):

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 (Aug 30, 2022): 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 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#18334
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?