Re: make doc

[Carl Sorensen]

On 5/28/11 9:05 AM, "Graham Percival" <address@hidden> wrote:

> On Sat, May 28, 2011 at 03:47:11PM +0100, Phil Holmes wrote:
>> ----- Original Message ----- From: "Carl Sorensen"
>> <address@hidden> To: "Phil Holmes" <address@hidden>;
>> "Graham Percival" <address@hidden>
>>>> 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.
> 
> I disagree; those logs can be useful.  We just don't need to see
> them on the console.

I agree with your position.  I had forgotten about the individual log files.

> 
> Why not redirect the compile-output from each .ly to the
> appropriate .log file?  I mean, we *already* have a .log for each
> .ly file... what's in the .log file at the moment?  Why not put
> the --verbose output in there?  etc.
> 
> GUB does a really nice job of managing ouput information -- it
> (generally) doesn't overwhelm you with spam on the console, but
> whenever you want to see what the detailed output was at some
> step, it's either in the log/ dir (for general GUB stuff) or the
> relevant target/architecture/log/ dir.
> 
> I'd like to see a similar thing here.  Don't remove output; just
> save it to files.

Even better.

Carl