Graham Percival writes: > I still don't feel that we have any kind of consensus on this. > Here's an updated proposal.
Ah, great. So what if we add a --log option to lilypond-book (and probably to lilypond), that [always in verbose mode?] writes individual .log files alongside the output. Would this fix 90% of this proposal? Sure, we also have metafont/post, fontforge. I can imagine also adding stepmake rules to handle V=0 for c/c++ compilation. Possibly not logging that would be OK, because a new compile with V=1 would almost instantly show the problem? Jan -- Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
