Last modified: 2013-12-18 19:11:07 UTC
In the case of lilypond syntax errors, it really shouldn't carry on and try and push it through ghostscript. Extracting the error and showing it to the user would be good e.g. from bug 47534 Processing `.../file.ly' Parsing... .../file.ly:14:0: error: syntax error, unexpected \header \header { .../file.ly:34:24: error: syntax error, unexpected '}' }Interpreting music... [8] Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `file.eps'... Converting to PNG...GS exited with status: 9
I guess if reedy fixes up the mediawiki install and fix GS error 9 all the error message will be invisible. Good question _how_ should the extension notify the user if there's seemingly some useful score output emitted...
Note, the random syntax errors I have made don't have the GS error 9, but instead look something like: Processing `/tmp/MWLP.ebe90cf9bcc69ad96d400911052e46f2/file.ly' Parsing... /tmp/MWLP.ebe90cf9bcc69ad96d400911052e46f2/file.ly:12:1: error: syntax error, unexpected SCM_TOKEN #(set-global-staff-size 14) /tmp/MWLP.ebe90cf9bcc69ad96d400911052e46f2/file.ly:25:24: error: syntax error, unexpected '}' }Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `file.ps'... Converting to PNG... error: failed files: "/tmp/MWLP.ebe90cf9bcc69ad96d400911052e46f2/file.ly" exited with status: 1
I'm going to mark wontfix. All the GS status 9 are all the same error (out of memory)
