In the *NIX world, this isn’t a problem because *NIX provides a “Pseudo Terminal” (PTY) infrastructure which makes it easy to build the communication plumbing for a Console or service, but Windows does not …īefore we dig into what we’ve done, let’s briefly revisit how Terminals evolved: In the beginning was the TTYĪs discussed in the first ‘backgrounder’ post in this series, in the early days of computing, users operated computers via electromechanical Teletype (TTY) devices connected to a computer via some form of serial communications link (typically a 20mA current loop). When building a Console or service, developers need to be able to access/supply the communication pipes through which their Terminal/service communicates with command-line applications. ![]() One of those weaknesses is that Windows tries to be “helpful” but gets in the way of alternative and 3rd party Console developers, service developers, etc. We also discussed many of Console’s strengths and outlined its key weaknesses. In the previous post in this series, we started to explore the internals of the Windows Console and Windows’ Command-Line infrastructure. Introducing the Windows Pseudo Console (ConPTY).The Evolution of the Windows Command-Line. ![]() ![]() Note: This chapter list will be updated as more posts are published: Posts in the “Windows Command-Line” series In this, the fourth post in the Windows Command-Line series, we’ll discuss the new Windows Pseudo Console (ConPTY) infrastructure and API – why we built it, what it’s for, how it works, how to use it, and more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |