Re:Introducing the Windows Pseudo Console (ConPty)
by cryptonector on Wednesday August 15, 2018 @10:42PM
(#17771496)
The Windows Console was even more terminally dead. Terminals have their limitations, but honestly, I'll take a terminal, tty/pty, and terminfo, any day over the Windows Console.
Re:Introducing the Windows Pseudo Console (ConPty)
by caf on Wednesday August 15, 2018 @10:02PM
(#17771323)
You also have to sanitise untrusted data that you want to output.
Re:Introducing the Windows Pseudo Console (ConPty)
by cryptonector on Wednesday August 15, 2018 @10:16PM
(#17771371)
And remember to use less -R or else pipe to col(1) or whatever.
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"
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. (-:
Re:Introducing the Windows Pseudo Console (ConPty)
by quotemstr on Thursday August 16, 2018 @08:56AM
(#17774187)
Yeah, I know
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.
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.
The fragility of in-band signaling in the TTY world is not *nix's fault or anything. VMS had that too, since VMS too had to deal with TTYs. The fact is that a) the system evolved from real, hardware TTYs of the 1970s, b) using a text stream with some in-band signaling doesn't even half suck -- mostly it rocks, and all you have to do for it to rock is get the right $TERM value and not output binary files to the tty.