On Wed, Jul 13, 2011 at 11:04:18PM +0100, Trevor Daniels wrote: > > Graham Percival wrote Wednesday, July 13, 2011 5:57 PM > > >On Wed, Jul 13, 2011 at 03:26:18PM +0100, Phil Holmes wrote: > > >That "worst that happens" is beyond what's acceptable. Seeing an > >error message before the command that causes the error? That > >could easily chew up 10 hours of fruitless debugging while > >somebody investigates a perfectly good command. > > > >In light of this, let's go ahead with the separate log files for > >now. > > If the relative order of the messages to stdout and > stderr is important, how come it's better to completely > lose the relative order by placing them in separate > files? If we are to remove messages from the console > then surely they must be interleaved properly in a single > file.
Hmm, that's a moot point (old UK definition). > If a way can't be found for doing this I don't > see how we can change the present system - or have I > missed something? Hmm, that's a moot point (current US definition). At the moment, lilypond only produces messages on stderr. So lilypond-book --redirect-lilypond-output will produce a 0-byte .log file and a 1234+-byte .err.log file. If we think that lilypond might ever produce separate output on stdout and stderr, then keeping two logfiles might possibly be useful (although there's still the concern about losing relative order between the two). If we think that lilypond will never produce logging messages on stdout, then I suppose that it might make more sense to send stderr to the .log file, and omit stdout "logging" entirely (as there would never be anything to log). 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 you can tell, I'm not really "on top" of lilypond these days. I'd forgotten how distracting jetlag+family+cat were. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
