----- Original Message -----
From: "Graham Percival" <gra...@percival-music.ca>
To: "David Kastrup" <d...@gnu.org>
Cc: <lilypond-devel@gnu.org>
Sent: Thursday, June 16, 2011 5:40 PM
Subject: Re: Patch: small reduction in output from make doc
On Thu, Jun 16, 2011 at 04:48:36PM +0200, David Kastrup wrote:
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.
How would that play with (presumably poor) terminal support on
mingw, and even worse, various "graphical" apps like lilypad,
jedit, frescobaldi, etc? I like that idea for normal linux usage,
but I don't think we should switch to that system without knowing
how it would affect other programs which call lilypond.
TBH, I don't agree at all. I personally think there's nothing worse than a
process that takes place in the background and gives no indication that
anything is happening. I've frequently interrupted git grep for this
reason - just to see if it's actually doing something. My response would
be - in Unix, if you don't want to see the "normal" output, then add a
1>/dev/null - it's simple enough.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
