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-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 of us apparently have at home :-) 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 1/1023 2/1023 3/1023 ... would also suffice as a progress indicator. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: verbosity of `make doc'
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 so long is the lilypond-book --tons-of-flags all_regtests_at_once.tely command. (same for NR chapters) 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. Potentially we could print the name of the log file, so that you could tail out-www/Documentation/notation/spacing.log to view the progress...? but I'm not certain this can be done cleanly in our build system. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: verbosity of `make doc'
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 lilypond-book's subprocesses to files, together with other useful information, while printing something different to the console. However, since I can't implement this by myself, I'll shut up now :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: verbosity of `make doc'
- 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-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 of us apparently have at home :-) 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 1/1023 2/1023 3/1023 ... would also suffice as a progress indicator. Werner I tend to use the CPU meter as a progress indicator. If it's 100%, make doc is progressing... -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
