Not really, consider the use case of a TUI-ish application showing some progress bar. Having both stdout and stderr doesn’t solve the use case of wanting the terminal to know when it’s done. (in fact using both only makes the problem worse for the user by garbling the text!)
Ignoring the fact stdout/stderr are already too widely used to force an in-band protocol on top of them, also consider a TUI-ish application that itself spawns 4 other applications that themselves have their own concept of progress. (Directed at linkdd, but piggybacking on agreeing with parents comment)
Isn’t that why we have both stdout and stderr ?
score 1 · canonical
Not really, consider the use case of a TUI-ish application showing some progress bar. Having both stdout and stderr doesn’t solve the use case of wanting the terminal to know when it’s done. (in fact using both only makes the problem worse for the user by garbling the text!)
score 1 · canonical
Ignoring the fact stdout/stderr are already too widely used to force an in-band protocol on top of them, also consider a TUI-ish application that itself spawns 4 other applications that themselves have their own concept of progress. (Directed at linkdd, but piggybacking on agreeing with parents comment)
score 1 · canonical