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

DISCUSSION: An example of running terminal (either Windows Terminal, or conhost) attached to pseudo console #12104

New Issue
Open
opened 2026-01-31 03:06:27 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:06:27 +00:00
Owner
Copy Link

Originally created by @vvavrychuk on GitHub (Jan 18, 2021).

I would like to feed/consume pseudo console pipes from my application and have some terminal (either Windows Terminal, or conhost) connected to this pseudo console. This is almost like https://github.com/microsoft/terminal/tree/main/samples/ConPTY/EchoCon but a little bit reversed. In EchoCon, application that feeds pseudo console (ping) is running as a separate process and current process is assumed to be run from terminal. But I want current process to feed pseudo console (current process can be run from terminal or not, it should not matter), and some terminal should be run from my application connected to pseudo console in a separate window.

The background is that I am porting application from Linux which uses multiple pseudo-consoles in one process. It is reading and writing to/from them in one thread sequentially. And it spawns multiple xterms connected to those pseudo consoles.

If I create multiple Windows pseudo consoles in one process, how can I spawn multiple terminal applications (conhost.exe?, Windows Terminal) to output content of those pseudo consoles?

Originally created by @vvavrychuk on GitHub (Jan 18, 2021). I would like to feed/consume pseudo console pipes from my application and have some terminal (either Windows Terminal, or conhost) connected to this pseudo console. This is almost like https://github.com/microsoft/terminal/tree/main/samples/ConPTY/EchoCon but a little bit reversed. In EchoCon, application that feeds pseudo console (ping) is running as a separate process and current process is assumed to be run from terminal. But I want current process to feed pseudo console (current process can be run from terminal or not, it should not matter), and some terminal should be run from my application connected to pseudo console in a separate window. The background is that I am porting application from Linux which uses multiple pseudo-consoles in one process. It is reading and writing to/from them in one thread sequentially. And it spawns multiple xterms connected to those pseudo consoles. If I create multiple Windows pseudo consoles in one process, how can I spawn multiple terminal applications (conhost.exe?, Windows Terminal) to output content of those pseudo consoles?
claunia added the Issue-QuestionNeeds-Tag-Fix labels 2026-01-31 03:06:27 +00:00
claunia commented 2026-01-31 03:06:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 19, 2021):

Okay so it might be helpful to have additional terminology defined here.

  • a "commandline client" application is something like ping, bash, etc. It's a application that emits text output and reads text input.
  • a "terminal" application is something that can be used for displaying the text output by a client app, and can read input from the OS and send it to a client app.

So it sounds like you have a client app that needs to output to multiple terminals all at once, correct? Kinda like a reverse tmux, correct? We can try helping come up with a clever solution, but I want to make sure we understand the scenario fully.

@zadjii-msft commented on GitHub (Jan 19, 2021): Okay so it might be helpful to have additional terminology defined here. * a "commandline **client**" application is something like `ping`, `bash`, etc. It's a application that emits text output and reads text input. * a "**terminal**" application is something that can be used for displaying the text output by a client app, and can read input from the OS and send it to a client app. So it sounds like you have a client app that needs to output to multiple terminals all at once, correct? Kinda like a reverse `tmux`, correct? We can try helping come up with a clever solution, but I want to make sure we understand the scenario fully.
claunia commented 2026-01-31 03:06:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 23, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jan 23, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 03:06:28 +00:00
Author
Owner
Copy Link

@vvavrychuk commented on GitHub (Jan 24, 2021):

@zadjii-msft you are absolutely right!

I have tried to code example here https://github.com/vvavrychuk/multipty-example/blob/master/multipty.c

It opens given number of ptys and launches xterm for each using -S flag. If user types something in xterm, it returns back to main application
Screenshot from 2021-01-25 01-06-16

There should be also a way to type client id and message in main application and it will be sent to corresponding client, but that's not finished in this example.

Also, I should probably use non-buffered IO...

@vvavrychuk commented on GitHub (Jan 24, 2021): @zadjii-msft you are absolutely right! I have tried to code example here https://github.com/vvavrychuk/multipty-example/blob/master/multipty.c It opens given number of ptys and launches xterm for each using -S flag. If user types something in xterm, it returns back to main application ![Screenshot from 2021-01-25 01-06-16](https://user-images.githubusercontent.com/152563/105646888-17fff100-5eab-11eb-8b1a-826ab256bd0e.png) There should be also a way to type client id and message in main application and it will be sent to corresponding client, but that's not finished in this example. Also, I should probably use non-buffered IO...
claunia commented 2026-01-31 03:06:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 28, 2021):

I'm going to take triage off this, but keep it open as a discussion question. 😄 Thanks!

@DHowett commented on GitHub (Jan 28, 2021): I'm going to take triage off this, but keep it open as a discussion question. :smile: 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 Issue-Question Needs-Tag-Fix
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#12104
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?