On 6/16/11 8:48 AM, "David Kastrup" <d...@gnu.org> wrote: > Carl Sorensen <c_soren...@byu.edu> writes: > >> David Kastrup feels pretty strongly that progress messages belong on >> stderr along with warning/error messages, since ther are not the >> output of the program. > > Actually, I feel progress messages belong on /dev/null. Iff stderr is > on a tty, there may be some justification to put out some progress > indicators to it, but they should not take useful space: one can > compress successive progress messages by using CR and/or BS when going > on.
Sorry to mischaracterize your statement. On rereading it, it would have been more accurate to say "David Kastrup feels pretty strongly that progress messages don't belong on stdout." Thanks for the clarification. Carl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
