How do I do that? I tried closing the input pipe but CMD.EXE is still waiting for more my use of the VS 2019 command prompts are all with cmd.exe, not Windows Terminal. I expect that CMD.EXE to end (same as it does when the input ends on ConHost. I´ve written all the desired input to the input stream and I want to signal that the input has come to an end. Now, I have a C# app that is using CreatePseudoConsole Api to call a console App (let's say it is CMD). For example do CMD /c < SomeEmptyFile.txt. When StdIn is closed or EOF arrives, the console app knows, stops waiting and closes. I am talking about console apps specifically, that reads from StdIn. you actually are calling a CMD.EXE console app batch that launches a windows app, confusing but totally unrelated. VSCode is a Win App with a code.cmd file in the path that wraps it, thus when you code. A console app will block the console, a windows app would not. You are describing the issue that an EXE file can be of different types. This question is not about the Windows Terminal app, but how to use the PseudoConsole API (ConPty). Hi we are talking about different things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |