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

Phrasing Q #11714

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

Originally created by @DamieFC on GitHub (Dec 5, 2020).

I know there's 1,000+ other issues that are more important, but by "the original Windows console host," do you mean cmd.exe, or something else? Again, this isn't important, it's a least priority issue.

Thank you!

Originally created by @DamieFC on GitHub (Dec 5, 2020). I know there's 1,000+ other issues that are more important, but by "the original Windows console host," do you mean cmd.exe, or something else? Again, this isn't important, it's a least priority issue. Thank you!
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:55:32 +00:00
claunia commented 2026-01-31 02:55:33 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 5, 2020):

Sure! So, the black window that opens when you run cmd (and the blue one for Windows Powershell) or any other text-based application is actually provided by one program: “conhost”. It is the Windows CONsole HOST, and it actually makes all the console APIs work. It gives those applications a screen, and lets the user actually interact with them.

This repository contains that application in addition to Terminal (because they share code), and the version of it you can build (“OpenConsole”) is nearly identical to the one that comes with Windows (conhost.exe) (but much, much more up to date!)

Hope that helps! Feel free to ask any followups 😄

@DHowett commented on GitHub (Dec 5, 2020): Sure! So, the black window that opens when you run cmd (and the blue one for Windows Powershell) or any other text-based application is actually provided by one program: “conhost”. It is the Windows CONsole HOST, and it actually makes all the console APIs work. It gives those applications a screen, and lets the user actually interact with them. This repository contains that application in addition to Terminal (because they share code), and the version of it you can build (“OpenConsole”) is nearly identical to the one that comes with Windows (`conhost.exe`) (but much, much more up to date!) Hope that helps! Feel free to ask any followups 😄
claunia commented 2026-01-31 02:55:33 +00:00
Author
Owner
Copy Link

@DamieFC commented on GitHub (Dec 5, 2020):

Ok! Thank you 😄!

@DamieFC commented on GitHub (Dec 5, 2020): Ok! Thank you 😄!
claunia commented 2026-01-31 02:55:33 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 6, 2020):

(I'll close this one as an Answered Question, but don't let that stop you from bumping it if you want!)

@DHowett commented on GitHub (Dec 6, 2020): (I'll close this one as an Answered Question, but don't let that stop you from bumping it if you want!)
claunia commented 2026-01-31 02:55:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 6, 2020):

@DHowett (This is off-topic but this is the perfect place to ask another question without creating a new issue)

Recently I believe clickable links were added to con host

But when I unzipped the latest preview msix and took out OpenConsole.exe, clickable links doesn't seem to work!

@ghost commented on GitHub (Dec 6, 2020): @DHowett (This is off-topic but this is the perfect place to ask another question without creating a new issue) Recently I believe clickable links were added to con host But when I unzipped the latest preview msix and took out OpenConsole.exe, clickable links doesn't seem to work!
claunia commented 2026-01-31 02:55:33 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 6, 2020):

Clickable links were actually not added to conhost; the infrastructure for supporting both OSC8 and autodetected links was, because (for OSC8) conpty needs to be able to communicate them to Terminal/VSCode/wezterm/... and (for autodetection) the code for the text buffer is shared between conhost and terminal!

@DHowett commented on GitHub (Dec 6, 2020): Clickable links were actually _not_ added to conhost; the infrastructure for supporting both OSC8 and autodetected links was, because (for OSC8) conpty needs to be able to communicate them to Terminal/VSCode/wezterm/... and (for autodetection) the code for the text buffer is shared between conhost and terminal!
claunia commented 2026-01-31 02:55:34 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 6, 2020):

The “interactivity” layer in conhost was not hooked up for OSC8 links, and neither was the GDI renderer. The patten detector was not hooked up for autodetected links 😄

@DHowett commented on GitHub (Dec 6, 2020): The “interactivity” layer in conhost was not hooked up for OSC8 links, and neither was the GDI renderer. The patten detector was not hooked up for autodetected links 😄
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-Question Needs-Tag-Fix Resolution-Answered
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#11714
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?