----- Original Message -----
From: "Carl Sorensen" <c_soren...@byu.edu>
To: "Phil Holmes" <m...@philholmes.net>; "Graham Percival"
<gra...@percival-music.ca>
> OK - one of the first things I see is that lilypond is always invoked
> with
> the --verbose flag - so each time we call lilypond (and it's quite a
> bit -
> over 180 as an estimate from grep) we get 100s of lines of lilypond
> debug
> output - this probably adds 20-30,000 lines to the output. My
> suggestion
> for task 1 is to get rid of the --verbose flag. Any idea why it's
> there?
So we can see which scm files are loaded, etc. It's very helpful in
debugging problems.
Certainly lose it with the -s flag.
Carl
Ah. That takes me back to a debate I had with Graham over the website
build. I'd originally written it so that you got most of the "traditional"
output with make website, but lost all of this (and the make echo) with
make -s website - so you effectively could run silent except for real
warnings, or see all output. In the end it was decided that the -s flag
would only determine whether you see make echo, not whether other output is
generated. So if we follow this approach with docs, we'd get rid of
verbose, full stop.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel