On 29/12/15 08:52, Werner LEMBERG wrote:
> Is there a particular reason to no making `QUIET_BUILD' the default?
> For Metafont, it's extremely chatty otherwise...
>
> On the other hand, I suggest to change
>
> ifdef QUIET_BUILD
> LILYPOND_BOOK_WARN = --l
Is there a particular reason to no making `QUIET_BUILD' the default?
For Metafont, it's extremely chatty otherwise...
On the other hand, I suggest to change
ifdef QUIET_BUILD
LILYPOND_BOOK_WARN = --loglevel=NONE
else
LILYPOND_BOOK_WARN = --loglevel=WARN
endif
to
ifdef QUIET_BUILD
Am 29.12.2015 um 09:52 schrieb Werner LEMBERG:
Is there a particular reason to no making `QUIET_BUILD' the default?
For Metafont, it's extremely chatty otherwise...
I prefer a verbose build and a script to save the chatty output to a logfile:
#!/bin/bash
RED='\033[0;31m'
NOC='\033[0m
>> Is there a particular reason to no making `QUIET_BUILD' the
>> default? For Metafont, it's extremely chatty otherwise...
>
> I prefer a verbose build and a script to save the chatty output to a
> logfile:
Well, the Metafont logging data is *always* saved to
