----- Original Message -----
From: "Phil Holmes" <m...@philholmes.net>
To: "Reinhold Kainhofer" <reinh...@kainhofer.com>; <lilypond-devel@gnu.org>
Sent: Wednesday, June 15, 2011 5:51 PM
Subject: Re: Patch: small reduction in output from make doc
----- Original Message -----
From: "Reinhold Kainhofer" <reinh...@kainhofer.com>
To: <lilypond-devel@gnu.org>
Sent: Wednesday, June 15, 2011 5:02 PM
Subject: Re: Patch: small reduction in output from make doc
Am Mittwoch, 15. Juni 2011, 16:22:14 schrieb Phil Holmes:
2>&1 sends error and normal output to the same place.
Hmm, doesn't that defeat the whole purpose of error messages?
I mean, by this you are HIDING the error messages, too. The current
problem
with the make output is that a plethora of useless progress messages are
hiding those few error messages that would be really useful to be seen.
Hiding all error messages together with the progress messages is throwing
out
the baby with the bath water (as we say here in German).
I can't say I disagree. As it stands, however, my initial goal is to get
the output down to a readable amount full stop - if that means discarding
a few error messages thrown by LilyPond in compiling lily files to create
midi files, I'm not sure I'd be too worried. It's trivial to reduce the
redirect to output information only, and once again show errors on the
terminal.
I think there's another problem with this. If I run
lilypond test.ly 1> test.log
it should redirect non-error output to the file, and errors should appear in
the terminal. In contrast,
lilypond test.ly 2> test.log
errors are in the log, normal output to terminal. In practice, I see all
output appearing in the terminal in the first line, and the logfile in the
second line. Does lily distinguish between error and normal output?
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
