Re: Adds redirect-lilypond-output option tolilypond-book(issue4664060)

[Phil Holmes]

----- Original Message ----- 
From: "Graham Percival" <address@hidden>
> Perhaps, in yet another stunning example of mis-management, this
> entire patch should be withdrawn pending the GOP stdout/stderr
> discussion.  The introduction of that discussion is pending us
> finally finishing the C++ question, which itself is pending
> another policy update, which itself was delayed due to my
> travelling.


As it stands, this patch does nothing unless you turn on the 
redirect-lilypond-output for lilypond book, so it's zero impact unless 
anyone deliberately uses it.  It then sends a null stream (lilypond's stdout 
output) to one file and an output stream (lilypond's stderr output) to 
another.  So there's a 0% possibility of output being mixed, since you can't 
mix something with nothing and get a different result.

In the event that some of lilypond's output were sent to stdout, this would 
have to be done such that the 2 streams (stdout and stderr) are usable on 
their own.  Otherwise the buffering idiosyncrasies of the OS are always 
going to cause problems.

Given that this patch has zero effect unless it's deliberately used, and has 
zero effect of mixing, let's go with it now.

--
Phil Holmes