Sven Axelsson wrote:
It is even quainter. Running lilypond from the command prompt does generate correct output and no Wrong type error. Doubleclicking the *.ly file generates no output and a clean log, since warnings and errors are printed on stderr and doesn't end up in that log file. Using my Python build script that calls os.system() to run lilypond also fails in the same way and shows the warning and error, since I am redirecting both stdout and stderr to my log file.
Damn. That might be another GC bug. Can you send me the offending .ly file (privately)?
This is with 2.6.1 Windows stand alone. I don't think I can provide more information than this. Is there a formal bug report format I should use?
-- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
