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

Recognizing the new terminal as an application #11098

New Issue
Closed
opened 2026-01-31 02:38:32 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 02:38:32 +00:00
Owner
Copy Link

Originally created by @Bios-Marcel on GitHub (Oct 21, 2020).

Depending on what feature set is a available on a terminal, an application might want to act differently. For example, using emojis and such should be avoided in the old windows terminal. Is there some easy way, that applications can use to know they are running on the new version of the windows terminal? Whether this is possible or not, it would be great to mention this somewhere in /doc I assume.

Originally created by @Bios-Marcel on GitHub (Oct 21, 2020). Depending on what feature set is a available on a terminal, an application might want to act differently. For example, using emojis and such should be avoided in the old windows terminal. Is there some easy way, that applications can use to know they are running on the new version of the windows terminal? Whether this is possible or not, it would be great to mention this somewhere in `/doc` I assume.
claunia added the Resolution-DuplicateIssue-Docs labels 2026-01-31 02:38:32 +00:00
claunia commented 2026-01-31 02:38:33 +00:00
Author
Owner
Copy Link

@Bios-Marcel commented on GitHub (Oct 21, 2020):

Somebody just hinted me that the variable introduced with https://github.com/microsoft/terminal/pull/897 (WT_SESSION) could probably be used for this.

@Bios-Marcel commented on GitHub (Oct 21, 2020): Somebody just hinted me that the variable introduced with https://github.com/microsoft/terminal/pull/897 (`WT_SESSION`) could probably be used for this.
claunia commented 2026-01-31 02:38:33 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 21, 2020):

Applications should not attempt to detect whether they're running in WT. Any assumption they make will be invalidated with time. Any application that attempts to ascribe specific behavior to Windows Terminal will be wrong and cause unnecessary vendor lock-in when it inevitably fails to work on Hyper, Alacritty, Mintty, and ConEmu even though those terminals support all the same features.

For example, using emojis and such should be avoided in the old windows terminal.

This is only true today, and will not be true once the rendering engine in this repository converges with the one in Windows.

All of the code in this repository that pertains to the inbox console host eventually goes into Windows, and goes out into the "old" windows "terminal."

/dup #1060.

@DHowett commented on GitHub (Oct 21, 2020): Applications should not attempt to detect whether they're running in WT. Any assumption they make will be invalidated with time. Any application that attempts to ascribe specific behavior to Windows Terminal will be wrong and cause unnecessary vendor lock-in when it inevitably fails to work on Hyper, Alacritty, Mintty, and ConEmu even though those terminals support all the same features. > For example, using emojis and such should be avoided in the old windows terminal. This is only true today, and will not be true once the rendering engine in this repository converges with the one in Windows. All of the code in this repository that pertains to the inbox console host eventually goes into Windows, and goes out into the "old" windows "terminal." /dup #1060.
claunia commented 2026-01-31 02:38:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 21, 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 (Oct 21, 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 02:38:34 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 21, 2020):

Sorry, I meant /dup #1040!

@DHowett commented on GitHub (Oct 21, 2020): Sorry, I meant /dup #1040!
claunia commented 2026-01-31 02:38:34 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 21, 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 (Oct 21, 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!
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#11098
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?