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

Extend GetConsoleMode or add an new API set, to allow guest programs to distinguish CONHOST and Windows Terminal #1533

New Issue
Closed
opened 2026-01-30 22:29:44 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:29:44 +00:00
Owner
Copy Link

Originally created by @reli-msft on GitHub (Jun 5, 2019).

An equivalance to $TERM but more powerful:

HRESULT GetTerminalSupport(HANDLE hConsole, LPCWSTR featureName, INT *pSupport);

featureName may include "FontFallback", "Emoji", "Ligatures", etc.

Originally created by @reli-msft on GitHub (Jun 5, 2019). An equivalance to `$TERM` but more powerful: ```cpp HRESULT GetTerminalSupport(HANDLE hConsole, LPCWSTR featureName, INT *pSupport); ``` `featureName` may include "FontFallback", "Emoji", "Ligatures", etc.
claunia added the Issue-FeatureResolution-DuplicateArea-InteropProduct-Conpty labels 2026-01-30 22:29:44 +00:00
claunia commented 2026-01-30 22:29:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 6, 2019):

Hey @reli-msft, thanks for suggesting this.

Since we're in Windows, we're very, very hesitant to introduce additional APIs. They need board review, and we can only release new APIs with new versions of Windows. The sheer complexity of doing that, especially given that the long tail of applications will never use this particular one, gives me a lot of pause.

This one in particular is complicated by the fact that we'd need to extend the pseudoconsole protocol, which today is simply raw VT52/100/220 over two pipes (we'd like to keep it that way!), to support some modicum of feature detection requests... and then beg all future terminals that consume the pseudoconsole API to also play along by answering feature requests. It'd be a step backwards on our equitable participation in standards to ask that just yet.

I'd like to come to a good solution here, but I'm not sure a new API is it. We should probably converge the discussion over in #1040, which is practically the same thing. 😄

@DHowett-MSFT commented on GitHub (Jun 6, 2019): Hey @reli-msft, thanks for suggesting this. Since we're in Windows, we're very, very hesitant to introduce additional APIs. They need board review, and we can only release new APIs with new versions of Windows. The sheer complexity of doing that, especially given that the long tail of applications will never use this particular one, gives me a lot of pause. This one in particular is complicated by the fact that we'd need to extend the pseudoconsole protocol, which _today_ is simply raw VT52/100/220 over two pipes (we'd like to keep it that way!), to support some modicum of feature detection requests... and then beg all future terminals that _consume_ the pseudoconsole API to also play along by answering feature requests. It'd be a step backwards on our equitable participation in standards to ask that just yet. I'd like to come to a good solution here, but I'm not sure a new API is it. We should probably converge the discussion over in #1040, which is practically the same thing. :smile:
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 Area-Interop Issue-Feature Product-Conpty 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#1533
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?