Introducing the Windows Pseudo Console (ConPty)

Re:Introducing the Windows Pseudo Console (ConPty) by quotemstr on Thursday August 16, 2018 @12:29AM (#17771887)

I want a pipe2(2) flag or an fcntl or something that lets me signal "the other end of this pipe understands ANSI escapes"

[ Parent | on HN ]

Re:Introducing the Windows Pseudo Console (ConPty) by JdeBP on Thursday August 16, 2018 @06:50AM (#17773530)

First of all you have to define "ANSI escape".

Hints:

* You have the wrong country, on the wrong continent.

* It's not as simple in reality as your first answer will be. (-:

[ Parent | on HN ]

Re:Introducing the Windows Pseudo Console (ConPty) by quotemstr on Thursday August 16, 2018 @08:56AM (#17774187)

Yeah, I know

[ Parent | on HN ]

Re:Introducing the Windows Pseudo Console (ConPty) by caf on Thursday August 16, 2018 @12:45AM (#17771945)

I've considered before that you could allow each end of a pipe to set name/value attributes, which can be read by the other end.

[ Parent | on HN ]

Re:Introducing the Windows Pseudo Console (ConPty) by cryptonector on Thursday August 16, 2018 @01:19AM (#17772112)

And now you're reinventing the Windows Console API... :)

I mean, both approaches have their pluses, but the API approach is only ever going to work well for remoting if it is standardized and interoperable. And the installed base of Unix termcap/terminfo programs is huge, so plain old text-with-in-band-controls is not going away anytime soon.

[ Parent | on HN ]

Re:Introducing the Windows Pseudo Console (ConPty) by caf on Thursday August 16, 2018 @02:33AM (#17772409)

With things like SIGWINCH / ioctl(TIOCGWINSZ) we already know what kind of API it is, we are just haggling about the price.

[ Parent | on HN ]