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

Identify when PowerShell is running within Windows Terminal #14290

New Issue
Closed
opened 2026-01-31 04:06:21 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 04:06:21 +00:00
Owner
Copy Link

Originally created by @mileso on GitHub (Jun 21, 2021).

There is, by design, no reliable way. We have been hoping for someone to come along and explain what their use case would be for being able to determine that 😄

Originally posted by @DHowett-MSFT in https://github.com/microsoft/terminal/issues/5523#issuecomment-618809182

I'm your huckleberry 😀

Here is my use case:

Set a different window title when running PowerShell within Windows Terminal. Windows Terminal has less real estate because the title is displayed on a tab so I'd like to set a shorter title only when running under Windows Terminal.

Simple example: Add the path to the title only when not running within Windows Terminal.

Originally created by @mileso on GitHub (Jun 21, 2021). There is, by design, no reliable way. We have been hoping for someone to come along and explain what their use case would be for being able to determine that 😄 _Originally posted by @DHowett-MSFT in https://github.com/microsoft/terminal/issues/5523#issuecomment-618809182_ I'm your huckleberry 😀 Here is my use case: Set a different window title when running PowerShell within Windows Terminal. Windows Terminal has less real estate because the title is displayed on a tab so I'd like to set a shorter title only when running under Windows Terminal. Simple example: Add the path to the title only when not running within Windows Terminal.
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 04:06:21 +00:00
claunia commented 2026-01-31 04:06:22 +00:00
Author
Owner
Copy Link

@mileso commented on GitHub (Jun 21, 2021):

Here is my current work-around (I placed these lines in my profile script):

$parentProcess = (Get-Process -Id (gwmi win32_process -Filter "processid='$PID'").ParentProcessId)
$isWT = ($parentProcess.Name -like "Win*Term*")

@mileso commented on GitHub (Jun 21, 2021): Here is my current work-around (I placed these lines in my profile script): `$parentProcess = (Get-Process -Id (gwmi win32_process -Filter "processid='$PID'").ParentProcessId)` `$isWT = ($parentProcess.Name -like "Win*Term*")`
claunia commented 2026-01-31 04:06:23 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Jun 22, 2021):

how does this https://github.com/microsoft/terminal/issues/1040#issuecomment-496691842 sounds to you?

@skyline75489 commented on GitHub (Jun 22, 2021): how does this https://github.com/microsoft/terminal/issues/1040#issuecomment-496691842 sounds to you?
claunia commented 2026-01-31 04:06:23 +00:00
Author
Owner
Copy Link

@mileso commented on GitHub (Jun 22, 2021):

how does this #1040 (comment) sounds to you?

If you spawn a shell from within a Windows Terminal session it will inherit the WT environment variables so environment variables are not a solution. Or am I missing something from that discussion?

See: https://github.com/microsoft/terminal/issues/5523#issuecomment-619289717

@mileso commented on GitHub (Jun 22, 2021): > how does this [#1040 (comment)](https://github.com/microsoft/terminal/issues/1040#issuecomment-496691842) sounds to you? If you spawn a shell from within a Windows Terminal session it will inherit the WT environment variables so environment variables are not a solution. Or am I missing something from that discussion? See: https://github.com/microsoft/terminal/issues/5523#issuecomment-619289717
claunia commented 2026-01-31 04:06:23 +00:00
Author
Owner
Copy Link

@MartinGC94 commented on GitHub (Jun 22, 2021):

He also made a suggestion to check the parent process: (Get-Process -Id $PID).Parent.Name -eq "WindowsTerminal" this should never have false positives but it may have false negatives if you open up a nested process inside the terminal.

@MartinGC94 commented on GitHub (Jun 22, 2021): He also made a suggestion to check the parent process: `(Get-Process -Id $PID).Parent.Name -eq "WindowsTerminal"` this should never have false positives but it may have false negatives if you open up a nested process inside the terminal.
claunia commented 2026-01-31 04:06:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 6, 2021):

I mean, you can always just make the tabs wider too. See "tabWidthMode": "titleLength". If you're the kind of person who wants to put info into the terminal title, then you probably what the whole tab to be visible 😄

@zadjii-msft commented on GitHub (Jul 6, 2021): I mean, you can always just make the tabs wider too. See [`"tabWidthMode": "titleLength"`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/appearance#tab-width-mode). If you're the kind of person who wants to put info into the terminal title, then you probably what the whole tab to be visible 😄
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 Needs-Triage 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#14290
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?