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

window title not visible #11390

New Issue
Closed
opened 2026-01-31 02:46:18 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:46:18 +00:00
Owner
Copy Link

Originally created by @nExoRek on GitHub (Nov 13, 2020).

terminal is not publishing window title. as effect, when you try to debug in Visual Studio Code by attaching PID, all open sessions are indistinguishable /:
2020-11-13_12-39-25

Environment

Platform ServicePack Version VersionString

Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Steps to reproduce

run VSC, try using debugging by attaching to host pid

Expected behavior

have some distinguisher between processes - like e.g. window title.

Actual behavior

title is empty - only visible value is PID

Originally created by @nExoRek on GitHub (Nov 13, 2020). terminal is not publishing window title. as effect, when you try to debug in Visual Studio Code by attaching PID, all open sessions are indistinguishable /: ![2020-11-13_12-39-25](https://user-images.githubusercontent.com/22886046/99069045-e5ce3b00-25ad-11eb-8145-76bb8af77bfc.png) # Environment Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 # Steps to reproduce run VSC, try using debugging by attaching to host pid # Expected behavior have some distinguisher between processes - like e.g. window title. # Actual behavior title is empty - only visible value is PID
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:46:18 +00:00
claunia commented 2026-01-31 02:46:19 +00:00
Author
Owner
Copy Link

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

Okay maybe I'm not that familiar with VsCode, but how are you getting to that dialog to debug a powershell process? Is that something that's provided through an extension?

Are only powershell instances that are hosted in Terminal tabs not displaying their titles?

Which version of the Windows Terminal are you running?

@zadjii-msft commented on GitHub (Nov 13, 2020): Okay maybe I'm not that familiar with VsCode, but how are you getting to that dialog to debug a powershell process? Is that something that's provided through an extension? Are only powershell instances that are hosted in Terminal tabs not displaying their titles? Which version of the Windows Terminal are you running?
claunia commented 2026-01-31 02:46:19 +00:00
Author
Owner
Copy Link

@nExoRek commented on GitHub (Nov 13, 2020):

AFAIK it's not thru extension but built in 'remote debugging' feature which
reads PS process PIDs. the one with path on the screen is a regular PS
window.
if you debug PS it will show only PIDs of PS sessions, and i'm not using
other languages to tell.
not a big deal since there is $pid variable, but this may potentially have
some wider meaning, for other scenarios.

Windows Terminal
Version: 1.3.2651.0

pt., 13 lis 2020 o 13:26 Mike Griese notifications@github.com napisał(a):

@nExoRek commented on GitHub (Nov 13, 2020): AFAIK it's not thru extension but built in 'remote debugging' feature which reads PS process PIDs. the one with path on the screen is a regular PS window. if you debug PS it will show only PIDs of PS sessions, and i'm not using other languages to tell. not a big deal since there is $pid variable, but this may potentially have some wider meaning, for other scenarios. Windows Terminal Version: 1.3.2651.0 pt., 13 lis 2020 o 13:26 Mike Griese <notifications@github.com> napisał(a):
claunia commented 2026-01-31 02:46:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 17, 2020):

Unfortunately, Windows Terminal is a multi-process hosting environment. It cannot publish a window title for every instance of PowerShell that it is hosting.

Because the window is no longer owned by PowerShell, it will be necessary to find a workaround. Like you suggested, $PID is a good candidate.

Sorry!

@DHowett commented on GitHub (Nov 17, 2020): Unfortunately, Windows Terminal is a multi-process hosting environment. It cannot publish a window title for every instance of PowerShell that it is hosting. Because the window is no longer owned by PowerShell, it will be necessary to find a workaround. Like you suggested, `$PID` is a good candidate. Sorry!
claunia commented 2026-01-31 02:46:20 +00:00
Author
Owner
Copy Link

@nExoRek commented on GitHub (Nov 17, 2020):

thx for confirming.

wt., 17 lis 2020, 02:34 użytkownik Dustin L. Howett <
notifications@github.com> napisał:

@nExoRek commented on GitHub (Nov 17, 2020): thx for confirming. wt., 17 lis 2020, 02:34 użytkownik Dustin L. Howett < notifications@github.com> napisał:
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-Question Needs-Tag-Fix Resolution-Answered
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#11390
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?