Folks,
I really appreciate that `make doc' doesn't flood the console.
However, right now I see a long line calling lilypond-book.py which
sits there for already more than 15 minutes without any progress
indicator at all. This is perhaps too extreme and suitable only to
the supercomputers some
On Sat, Apr 07, 2012 at 08:56:15AM +0200, Werner LEMBERG wrote:
Wouldn't it be possible, similar to automake, that the name of the
currently processed file gets written to stdout, and that this
behaviour is the default? In case the names are meaningless, a simple
No, because what's taking
We're saving stdout and sterr to log files so we can keep the
output. Any additional info that lilypond-book prints would just be
saved to a file instead of screen.
There are more streams available than stderr and stdout, so it would
be actually possible to save stderr and stdout from
- Original Message -
From: Werner LEMBERG w...@gnu.org
To: lilypond-devel@gnu.org
Sent: Saturday, April 07, 2012 7:56 AM
Subject: verbosity of `make doc'
Folks,
I really appreciate that `make doc' doesn't flood the console.
However, right now I see a long line calling lilypond
