starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-09 02:26:45 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

support ENABLE_VIRTUAL_TERMINAL_PROCESSING per application #9687

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

Originally created by @mintty on GitHub (Jul 18, 2020).

VT escape sequence handling can be enabled by design with some Windows API call enabling the ENABLE_VIRTUAL_TERMINAL_PROCESSING mode.
(Refer https://github.com/microsoft/terminal/issues/6634#issuecomment-647726408).
There is also a registry feature to change the default to enable it (https://stackoverflow.com/questions/51680709/colored-text-output-in-powershell-console-using-ansi-vt100-codes/51681675#51681675).
However, it would be very useful to enable it per application, i.e. per executable, by some kind of property (settable via Explorer Properties menu and some kind of executable flag, e.g. via manifest). (Not sure whether https://github.com/microsoft/terminal/issues/2035 addresses this issue.)

Originally created by @mintty on GitHub (Jul 18, 2020). VT escape sequence handling can be enabled by design with some Windows API call enabling the ENABLE_VIRTUAL_TERMINAL_PROCESSING mode. (Refer https://github.com/microsoft/terminal/issues/6634#issuecomment-647726408). There is also a registry feature to change the default to enable it (https://stackoverflow.com/questions/51680709/colored-text-output-in-powershell-console-using-ansi-vt100-codes/51681675#51681675). However, it would be very useful to enable it per application, i.e. per executable, by some kind of property (settable via Explorer Properties menu and some kind of executable flag, e.g. via manifest). (Not sure whether https://github.com/microsoft/terminal/issues/2035 addresses this issue.)
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:00:54 +00:00
claunia commented 2026-01-31 02:00:55 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 13, 2020):

Hey, thanks for the request! Sorry to take so long to triage it. This is a specific case of #4954, so I'm going to close this out in favor of that. There's already some investigation underway over there 😄 where I'd like to make the input AND output states process-specific.

Having it be manifested would be pretty radical.

We've talked about having a new template for command-line applications in VS that sets nice defaults and pretty much communicates to the console subsystem that "this application is a well-behaved VT-only app" -- it would enable strict mode and passthrough mode and not allow buffer readout and all of the really annoying weird parts of the win32 API.

In general, /dup #4954

@DHowett commented on GitHub (Aug 13, 2020): Hey, thanks for the request! Sorry to take so long to triage it. This is a specific case of #4954, so I'm going to close this out in favor of that. There's already some investigation underway over there :smile: where I'd like to make the input AND output states process-specific. Having it be manifested would be pretty radical. We've talked about having a new template for command-line applications in VS that sets nice defaults and pretty much communicates to the console subsystem that "this application is a well-behaved VT-only app" -- it would enable strict mode and passthrough mode and not allow buffer readout and all of the really annoying weird parts of the win32 API. In general, /dup #4954
claunia commented 2026-01-31 02:00:56 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 13, 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 (Aug 13, 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-Feature 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#9687
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?