starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

How to embed cmd input box in another program? #1692

New Issue
Closed
opened 2026-01-30 22:33:53 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 22:33:53 +00:00
Owner
Copy Link

Originally created by @kernelbin on GitHub (Jun 15, 2019).

I want to use cmd inputbox in my own program, and I've tried many ways but none of them successed ( Include Create The conhost window as a child window, SetParent Function, and so on )
The might be many people want to use this powerful inputbox as well, And I wonder what should I do to make that.
Thanks !!!

Originally created by @kernelbin on GitHub (Jun 15, 2019). I want to use cmd inputbox in my own program, and I've tried many ways but none of them successed ( Include Create The conhost window as a child window, SetParent Function, and so on ) The might be many people want to use this powerful inputbox as well, And I wonder what should I do to make that. Thanks !!!
claunia commented 2026-01-30 22:33:54 +00:00
Author
Owner
Copy Link

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

For early 2019, you'll want to look at the pseudoconsole API -- a good starting point is here on MSDN, Creating a Pseudoconsole Session.

We're planning to make the TerminalControl and DirectWrite renderer/terminal buffer/VT parser components of Windows Terminal reusable and hostable for other applications. There's some work there going on in #1274 and #1263.

@DHowett-MSFT commented on GitHub (Jun 18, 2019): For early 2019, you'll want to look at the pseudoconsole API -- a good starting point is here on MSDN, [Creating a Pseudoconsole Session](https://docs.microsoft.com/en-us/windows/console/creating-a-pseudoconsole-session). We're planning to make the TerminalControl and DirectWrite renderer/terminal buffer/VT parser components of Windows Terminal reusable and hostable for other applications. There's some work there going on in #1274 and #1263.
claunia commented 2026-01-30 22:33:54 +00:00
Author
Owner
Copy Link

@kernelbin commented on GitHub (Jun 18, 2019):

For early 2019, you'll want to look at the pseudoconsole API -- a good starting point is here on MSDN, Creating a Pseudoconsole Session.

We're planning to make the TerminalControl and DirectWrite renderer/terminal buffer/VT parser components of Windows Terminal reusable and hostable for other applications. There's some work there going on in #1274 and #1263.

Thanks!

Is there any difference between creating a psedoconsole session and creating a new cmd exe process with hStdInput/hStdOutput set in STARTUPINFO ?

@kernelbin commented on GitHub (Jun 18, 2019): > For early 2019, you'll want to look at the pseudoconsole API -- a good starting point is here on MSDN, [Creating a Pseudoconsole Session](https://docs.microsoft.com/en-us/windows/console/creating-a-pseudoconsole-session). > > We're planning to make the TerminalControl and DirectWrite renderer/terminal buffer/VT parser components of Windows Terminal reusable and hostable for other applications. There's some work there going on in #1274 and #1263. Thanks! Is there any difference between creating a psedoconsole session and creating a new cmd exe process with hStdInput/hStdOutput set in STARTUPINFO ?
claunia commented 2026-01-30 22:33:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 18, 2019):

@yh-git Yes there is. When a commandline application is started with redirected input and output, it can't make use of the large majority of the Console API. For example, a user wouldn't be able to use the arrow keys to navigate the input line if cmd.exe was just created redirected. The Pseudoconosle API, however, does attach the commandline application to a full console, so the application can use the full console API. The pseudoconsole will then do the hard work of translating those API calls into a stream of characters, with VT sequences embedded in the output. You'll need to be able to handle a few types of VT sequences to be able to properly display pseudoconsole output.

@zadjii-msft commented on GitHub (Jun 18, 2019): @yh-git Yes there is. When a commandline application is started with redirected input and output, it can't make use of the large majority of the [Console API](https://docs.microsoft.com/en-us/windows/console/console-functions). For example, a user wouldn't be able to use the arrow keys to navigate the input line if cmd.exe was just created redirected. The Pseudoconosle API, however, does attach the commandline application to a full console, so the application can use the full console API. The pseudoconsole will then do the hard work of translating those API calls into a stream of characters, with VT sequences embedded in the output. You'll need to be able to handle a few types of VT sequences to be able to properly display pseudoconsole output.
claunia commented 2026-01-30 22:33:55 +00:00
Author
Owner
Copy Link

@kernelbin commented on GitHub (Jun 18, 2019):

@yh-git Yes there is. When a commandline application is started with redirected input and output, it can't make use of the large majority of the Console API. For example, a user wouldn't be able to use the arrow keys to navigate the input line if cmd.exe was just created redirected. The Pseudoconosle API, however, does attach the commandline application to a full console, so the application can use the full console API. The pseudoconsole will then do the hard work of translating those API calls into a stream of characters, with VT sequences embedded in the output. You'll need to be able to handle a few types of VT sequences to be able to properly display pseudoconsole output.

Thanks alot! pseudoconsole is just what i'm looking for, sounds attractive. I will try it.

@kernelbin commented on GitHub (Jun 18, 2019): > @yh-git Yes there is. When a commandline application is started with redirected input and output, it can't make use of the large majority of the [Console API](https://docs.microsoft.com/en-us/windows/console/console-functions). For example, a user wouldn't be able to use the arrow keys to navigate the input line if cmd.exe was just created redirected. The Pseudoconosle API, however, does attach the commandline application to a full console, so the application can use the full console API. The pseudoconsole will then do the hard work of translating those API calls into a stream of characters, with VT sequences embedded in the output. You'll need to be able to handle a few types of VT sequences to be able to properly display pseudoconsole output. Thanks alot! pseudoconsole is just what i'm looking for, sounds attractive. I will try it.
claunia commented 2026-01-30 22:33:55 +00:00
Author
Owner
Copy Link

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

I'm gonna close this one as it's been answered. Thanks!

@DHowett-MSFT commented on GitHub (Jun 18, 2019): I'm gonna close this one as it's been answered. Thanks!
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-TerminalControl Issue-Question Product-Meta 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#1692
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?