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

Include active sub process in tab title. #7164

New Issue
Closed
opened 2026-01-31 00:56:50 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 00:56:50 +00:00
Owner
Copy Link

Originally created by @cpietrzykowski on GitHub (Mar 26, 2020).

Description of the new feature/enhancement

With cmd.exe (for example) the title of the window includes the active process (when it differs from the shell). This would be welcome for Windows Terminal, most notably when there are multiple active tabs per host.

Proposed technical implementation details (optional)

Either append the process name to the tab title, or provide some profile customisation formats to give the user some control over what/when the tab title is automatically updated to reflect shell activity.

When a non-trivial sub process is started (say if the task takes longer than a few hundred millseconds), append the process name to the tab title.

Some shells support dynamic prompts, but I don't think they're all consistent with how events are triggered. (understanding that not all processes would be visible to the host -- i.e. Powershell -> ssh -> vi; would only result in the tab title being "ssh".)

I'd be happy to take a stab at implementing this if a more seasoned maintainer could point me in the right direction.

Originally created by @cpietrzykowski on GitHub (Mar 26, 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 With `cmd.exe` (for example) the title of the window includes the active process (when it differs from the shell). This would be welcome for `Windows Terminal`, most notably when there are multiple active tabs per host. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Either append the process name to the tab title, or provide some profile customisation formats to give the user some control over what/when the tab title is automatically updated to reflect shell activity. <!-- A clear and concise description of what you want to happen. --> When a non-trivial sub process is started (say if the task takes longer than a few hundred millseconds), append the process name to the tab title. Some shells support dynamic prompts, but I don't think they're all consistent with how events are triggered. (understanding that not all processes would be visible to the host -- i.e. Powershell -> ssh -> vi; would only result in the tab title being "ssh".) I'd be happy to take a stab at implementing this if a more seasoned maintainer could point me in the right direction.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:56:50 +00:00
claunia commented 2026-01-31 00:56:51 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 27, 2020):

Thanks for the request! I'd like for it to be part of the spec for #1320 -- we'll need to have a discussion about what we can do with our subprocess' token, and what makes sense to scrape to put in the title.

Mind moving future discussion for this feature over there?

Thanks!

/dup #1320

@DHowett-MSFT commented on GitHub (Mar 27, 2020): Thanks for the request! I'd like for it to be part of the spec for #1320 -- we'll need to have a discussion about what we can do with our subprocess' token, and what makes sense to scrape to put in the title. Mind moving future discussion for this feature over there? Thanks! /dup #1320
claunia commented 2026-01-31 00:56:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 27, 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 (Mar 27, 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!
claunia commented 2026-01-31 00:56:51 +00:00
Author
Owner
Copy Link

@cpietrzykowski commented on GitHub (Mar 27, 2020):

Thanks for the request! I'd like for it to be part of the spec for #1320 -- we'll need to have a discussion about what we can do with our subprocess' token, and what makes sense to scrape to put in the title.

Mind moving future discussion for this feature over there?

Thanks!

/dup #1320

No problem at all -- I assure you I searched countless times looking for a dupe, trying all manner of search terms.

@cpietrzykowski commented on GitHub (Mar 27, 2020): > Thanks for the request! I'd like for it to be part of the spec for #1320 -- we'll need to have a discussion about what we can do with our subprocess' token, and what makes sense to scrape to put in the title. > > Mind moving future discussion for this feature over there? > > Thanks! > > /dup #1320 No problem at all -- I assure you I searched countless times looking for a dupe, trying all manner of search terms.
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#7164
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?