Thanks for taking a look. Running from the command prompt when I get a truncated log file is an acceptable workaround for me. I'll leave it to the list's judgment whether to add this to the bug list or not.
Thanks again, Jay On Jan 29, 2008 8:44 AM, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > > > Trevor Daniels wrote: > > ... > > So there does seem to be a problem with capturing all > > the console output to the log file under XP. > > > Exactly! It's probably related to how the buffers are flushed when the > program terminates. Actually, it turns out that the difference is not > between > Windows and non-Windows since if you use > lilypond -dgui somefile.ly > from a command prompt, then you do get all the information into the .log > file. > If you instead run > lilypond-windows -dgui somefile.ly > (which is exactly what happens when you double-click on the file) then you > get the truncated .log file. The only difference between these two > executables > is that the -windows version is linked with gcc ... -mwindows. > Someone who's an expert in MinGW programming would probably be able to > fix the problem, but I have no clue whatsoever. > > /Mats >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
