Just curiosity, what's the size of this redirected output file? Secondly: let's assume it's a million lines worth (this much it seems to me). They take time to be printed. Compilation plus printing many megacharacters on screen or to a file takes much more than compilation alone. Therefore, it slowens the process in an appreciable amount, obvious, isn't it?
Sorry for bringing down the high technical level of this thread, but time has its importance. 2008/8/20 Reinhold Kainhofer <[EMAIL PROTECTED]>: > Am Mittwoch, 20. August 2008 schrieb John Mandereau: >> I usually redirect "make ewb" output to a file, so I don't see the problem. > > Sure, but it makes the output of make web a lot harder to read (currently > it's >>100.000 lines) and scan through to see when something was compiled. > > It's no problem, I was just wondering why we are cluttering the make web > output by things we only need to debug the build system. Similarly, why do we > call lilypond-book always with --verbose? > > In general, we don't need that verbose output, we need it only to debug the > buildsystem. Can't we have an env variable, say DEBUG_BUILDSYSTEM, and > use --verbose only in that case (we can then also remove the -q for > texi2pdf). -- Francisco Vila. Badajoz (Spain) http://www.paconet.org _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
