starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Recognize the new Windows Terminal from a PowerShell script #3153

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

Originally created by @developer82 on GitHub (Aug 5, 2019).

I'm writing a new PowerShell script, and I want to make use of unicode emojies, which are now supported by the new Windows Terminal Preview. However, for a user running "legacy" PowerShell that doesn't support it, I do not wish to show the unrecognized characters, and instead I would like to show him some other text/sign.

To be more simple - I would like to know when my PS script is running in the new Terminal and show one thing and show something else for other PS terminals.

I have tried using $env:TERM_PROGRAM. If I use is inside the vscode PS terminal it returns "vscode", but under normal PS terminal or new terminal it returns nothing.

Any ideas?

Originally created by @developer82 on GitHub (Aug 5, 2019). I'm writing a new PowerShell script, and I want to make use of unicode emojies, which are now supported by the new Windows Terminal Preview. However, for a user running "legacy" PowerShell that doesn't support it, I do not wish to show the unrecognized characters, and instead I would like to show him some other text/sign. To be more simple - I would like to know when my PS script is running in the new Terminal and show one thing and show something else for other PS terminals. I have tried using `$env:TERM_PROGRAM`. If I use is inside the vscode PS terminal it returns "vscode", but under normal PS terminal or new terminal it returns nothing. Any ideas?
claunia added the Resolution-DuplicateIssue-Docs labels 2026-01-30 23:14:14 +00:00
claunia commented 2026-01-30 23:14:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2019):

I believe we added a WT_SESSION environment variable for specifically this purpose.

WT_SESSION=e1d171d9-4739-4cd0-b086-50d729f39631

(where the value is a random GUID generated at runtime, per-terminal instance)

I don't think this is necessarily the right solution but I know it'll work, and I don't have any other ideas at the moment. I know there's some discussion around the idea of TERM_PROGRAM and if it's a good or bad idea somewhere else on this issue tracker, but I'm too lazy to look it up right now.

@zadjii-msft commented on GitHub (Aug 5, 2019): I believe we added a `WT_SESSION` environment variable for specifically this purpose. ``` WT_SESSION=e1d171d9-4739-4cd0-b086-50d729f39631 ``` (where the value is a random GUID generated at runtime, per-terminal instance) I don't think this is necessarily the right solution but I know it'll work, and I don't have any other ideas at the moment. I know there's some discussion around the idea of `TERM_PROGRAM` and if it's a good or bad idea somewhere else on this issue tracker, but I'm too lazy to look it up right now.
claunia commented 2026-01-30 23:14:15 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 5, 2019):

This is fundamentally a duplicate of #1040.

@DHowett-MSFT commented on GitHub (Aug 5, 2019): This is fundamentally a duplicate of #1040.
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-Docs 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#3153
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?