zadjii-msft
commented
3 years ago 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.
ghost
vvavrychuk
DHowett
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?