On Mon, Jul 04, 2011 at 04:23:06PM +0100, Phil Holmes wrote: > ----- Original Message ----- From: <percival.music...@gmail.com> > To: <philehol...@googlemail.com>; <em...@philholmes.net> > >Or maybe just make the "child returned" into "Error: could not complete > >command", or maybe "Error: child returned > >__insert_error_code_interpretation__" ? > > AFAICS this is a doddle to change. I'll do this as a follow up > piece of work unless you want it earlier.
Later piece of work is fine. I guess that now we'll wait for this patch to get onto the countdown. > >- it's a bit weird to see tons of output even when using the > >--redirect-lilypond-output. Would it be possible to make a > > --use-logfiles > >option which automatically turns on --redirect-lilypond-output, but also > >captures stderr+stdlog and writes *those* to a file? > >(and maybe in addition to writing the log file, it would display the > >"Error: child returned __blah_blah__" line) > > Don't think so, at present. From my reading of the Python, progress > and error messages mostly go to stderr, as does the error message. > To make it so that we don't see progress but do see the error > message would be something of a rewrite of how progress and errors > are handled in lilylib and lilypond-book. So, we need the GOP > debate on stderr versus stdout. ok, that makes sense. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
