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

How to determine if the current host can display emoji characters programmically #12451

New Issue
Open
opened 2026-01-31 03:16:00 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 03:16:00 +00:00
Owner
Copy Link

Originally created by @plastikfan on GitHub (Feb 7, 2021).

Is there a way to find out if the current host is Windows Terminal, Console, PowerShell ISE or any other host? I am asking this question from a PowerShell perspective (or any .Net Core api would suffice). I need to determine the characterstics of the currently running host and act accordingly. To be more specific, I have PowerShell functionality this displays emjoi's and as I am currently using Windows Terminal I have inadvertantly created functionality that will not work as I expected in the standard windows console.

In a powershell environment, we have access to a global variable $Host:

In Windows Terminal:

λ $host

Name             : ConsoleHost
Version          : 7.1.1
InstanceId       : ed19c947-594b-472c-abb5-d0d00306f1dd
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-GB
CurrentUICulture : en-GB
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

and in WIndows Console:

λ $host

Name             : ConsoleHost
Version          : 7.1.1
InstanceId       : ed19c947-594b-472c-abb5-d0d00306f1dd
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-GB
CurrentUICulture : en-GB
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

which are both exactly the same. I was hoping there would have been a property identifying it as the Windows Terminal or Console or any other such host type.

$host is of type: [System.Management.Automation.Host.PSHost.InternalHost], but looking through that documentation, I couldn't find anything that could help in this regard.

Alternatively, is there a way to determine if the host can render emojis? If the host is not capable of rendering unicode emojis then I need to take alternative action, (ie display alternative ascii characters). The current behaviour of Windows Console.

To illustrate my problem here is the result of some powershell functionality:

  • Windows terminal:

help display-emojis win-term

  • Windows Console:

help display-emojis win-cons

As you can see, in Windows Terminal, the Mandatory and PipeValue fields contain ✔️ and ✖️ , but in WIndows Console we simply see an ugly un-identofyable placeholder characters. I need to be able to take evasive action and display an alternative ascii sequence instead.

Thanks.

Originally created by @plastikfan on GitHub (Feb 7, 2021). Is there a way to find out if the current host is Windows Terminal, Console, PowerShell ISE or any other host? I am asking this question from a PowerShell perspective (or any .Net Core api would suffice). I need to determine the characterstics of the currently running host and act accordingly. To be more specific, I have PowerShell functionality this displays emjoi's and as I am currently using Windows Terminal I have inadvertantly created functionality that will not work as I expected in the standard windows console. In a powershell environment, we have access to a global variable $Host: In Windows Terminal: ``` λ $host Name : ConsoleHost Version : 7.1.1 InstanceId : ed19c947-594b-472c-abb5-d0d00306f1dd UI : System.Management.Automation.Internal.Host.InternalHostUserInterface CurrentCulture : en-GB CurrentUICulture : en-GB PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy DebuggerEnabled : True IsRunspacePushed : False Runspace : System.Management.Automation.Runspaces.LocalRunspace ``` and in WIndows Console: ``` λ $host Name : ConsoleHost Version : 7.1.1 InstanceId : ed19c947-594b-472c-abb5-d0d00306f1dd UI : System.Management.Automation.Internal.Host.InternalHostUserInterface CurrentCulture : en-GB CurrentUICulture : en-GB PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy DebuggerEnabled : True IsRunspacePushed : False Runspace : System.Management.Automation.Runspaces.LocalRunspace ``` which are both exactly the same. I was hoping there would have been a property identifying it as the Windows Terminal or Console or any other such host type. $host is of type: [System.Management.Automation.Host.PSHost.InternalHost], but looking through that documentation, I couldn't find anything that could help in this regard. Alternatively, is there a way to determine if the host can render emojis? If the host is not capable of rendering unicode emojis then I need to take alternative action, (ie display alternative ascii characters). The current behaviour of Windows Console. To illustrate my problem here is the result of some powershell functionality: * Windows terminal: ![help display-emojis win-term](https://user-images.githubusercontent.com/49785914/107159531-9028e500-6988-11eb-9019-b787bdf6659c.jpg) * Windows Console: ![help display-emojis win-cons](https://user-images.githubusercontent.com/49785914/107159535-9d45d400-6988-11eb-9b51-0369f2ef12eb.jpg) As you can see, in Windows Terminal, the Mandatory and PipeValue fields contain ✔️ and ✖️ , but in WIndows Console we simply see an ugly un-identofyable placeholder characters. I need to be able to take evasive action and display an alternative ascii sequence instead. Thanks.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:16:00 +00:00
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 Needs-Tag-Fix Needs-Triage
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#12451
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?