Introducing the Windows Pseudo Console (ConPty)

Re:Introducing the Windows Pseudo Console (ConPty) by JdeBP on Thursday August 16, 2018 @07:25AM (#17773681)

The sad thing is that this was all already implemented and done in Microsoft's second POSIX subsystem for Windows NT. It provided signals and process groups support for job control shells. It had a full control sequence interpreter for output and control sequence generator for extended keys. There were termcap/terminfo database records that people had added to other operating systems. It had a line discipline with "canonical" and "raw" modes. It had pseudo-terminals, with both BSD and System 5 access semantics.

* https://technet.microsoft.com/en-gb/library/bb497016.aspx

* https://technet.microsoft.com/en-gb/library/bb463219.aspx

* https://news.ycombinator.com/item?id=12866843

* http://jdebp.info./FGA/interix-terminal-type.html

And Microsoft owns it.

[ Parent | on HN ]

Re:Introducing the Windows Pseudo Console (ConPty) by quotemstr on Thursday August 16, 2018 @11:48AM (#17775683)

I wish people would stop pointing at the Linux subsystem and using it as an example of the stuff Windows in general could do. The Linux subsystem is a subsystem. In NT terminology, that makes it practically a container. It's disconnected from the rest of the system. It can interact with the win32 world in only a few constrained ways. You can't deliver SIGWINCH to a win32 process!

[ Parent | on HN ]

Re:Introducing the Windows Pseudo Console (ConPty) by JdeBP on Thursday August 16, 2018 @01:04PM (#17776461)

Actually, the second POSIX subsystem could deliver signals to Win32 processes. Who pointed at the Linux subsystem, by the way?

* https://news.ycombinator.com/item?id=11416392

[ Parent | on HN ]