Error Failed Files Lilypond
Warnings Errors Progress and Debug Output][ Up :Warnings Errors Progress and Debug Output][ > ] Available log levels LilyPond has several loglevels, which specify how verbose the output on the console should be: NONE: No output at all, even on failure ERROR: Only error messages WARN: Only error messages and warnings BASIC_PROGRESS: Warnings, errors and basic progress (success, etc.) PROGRESS: Warnings, errors and full progress messages INFO: Warnings, errors, progress and more detailed information (default) DEBUG: All messages, including full debug messages (very verbose!) The loglevel can either be set with the environment variable LILYPOND_LOGLEVEL or on the command line with the ‘--loglevel=...’ option. [ << Programming work][Top][Contents][Index][ ? ][Release work >> ][ < ][ Up :Warnings Errors Progress and Debug Output][ > ] Functions for debug and log output LilyPond has two different types of error and log functions: If a warning or error is caused by an identified position in the input file, e.g. by a grob or by a music expression, the functions of the Input class provide logging functionality that prints the position of the message in addition to the message. If a message can not be associated with a particular position in an input file, e.g. the output file cannot be written, then the functions in the flower/include/warn.hh file will provide logging functionality that only prints out the message, but no location. There are also Scheme functions to access all of these logging functions from scheme. In addition, the Grob class contains some convenience wrappers for even easier access to these functions. The message and debug functions in warn.hh also have an optional argument newline, which specifies whether the message should always start on a new line or continue a previous message. By default, progress_indication does NOT start on a new line, but rather continue the previous output. They also do not have a particular input position associated, so there are no progress functions in the Input class. All other functions by default start their output on a new line. The error functions come in three different flavors: fatal error messages, programming error messages and normal error messages. Errors written by the error () function will cause LilyPond to exit immediately, errors by Input::error () will continue the compilation, but return a non-zero return value of the lilypond call (i.e. indicate an unsuccessful program execution). All other errors will be printed on the console, but not exit LilyPond or indic
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Urs Liska
writes: > Am 17.04.2016 um 12:33 schrieb David Kastrup: >> Urs Liska writes: >> >>> Am 17. April 2016 10:51:34 MESZ, schrieb David Kastrup : >>>> Urs Liska writes: >>>> >>>>> Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup : >>>>> >>>>>> A warning is appropriate for something which is not an error: namely >>>>>> LilyPond has a well-specified task but the results will not likely >>>>>> make sense. LilyPond does not return an error code for a warning. >>>>> Well, then let LilyPond report an error when it encounters one. But >>>>> only then a "fatal" one when it actually forces LilyPond to stop. >>>> For any _correct_ input, LilyPond is eventually forced http://lilypond.org/doc/v2.18/Documentation/contributor/warnings-errors-progress-and-debug-output to stop. >>> This is the point where I have to say you are talking bullshit, >>> deliberately (?) and arbitrarily flipping around everyone's words and >>> intentions. It doesn't make sense to continue with that thread. >> So what does "force to stop" mean in your opinion? > > \version "2.19.40" > > { > c' > > produces: > > /tmp/frescobaldi-hp7_ll/tmpoyBSnr/document.ly:4:4 <0>: error: syntax > error, unexpected end of input > > c > > ' https://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00378.html How is this substantially different from { c' } { here? GNU LilyPond 2.19.32 Processing `dog.ly' Parsing... dog.ly:2:2: error: syntax error, unexpected end of input { dog.ly:1: warning: no \version statement found, please add \version "2.19.32" for future compatibility Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `/tmp/lilypond-EZC6cx'... Converting to `dog.pdf'... Deleting `/tmp/lilypond-EZC6cx'... fatal error: failed files: "dog.ly" > fatal error: failed files: "/tmp/frescobaldi-hp7_ll/tmpoyBSnr/document.ly" > > and it is obivous that LilyPond wasn't able to produce a file. This is > the class of errors where I think the label "fatal" is appropriate. So in my example it did produce a file. The error was exactly the same kind of error. Now it is no longer fatal? Because there was something before the error that _did_ produce output? > No, of course not. If LilyPond is able to "recover" (as Andrew put it) > it should of course do so. But it should not report a "fatal error" > and a "failed file" then. So why is the above error no longer fatal, and why can one now consider LilyPond as having succeeded in compiling the file? > I would say if LilyPond is able to produce files for all targets that > are requested by the input file then the compilation didn't "fail". Ok, so now hewhen I test the example
into Lilypond format. I have tried loading the resulting .ly file into Frescobaldi and get the following error log; LilyPond [hornpipe.ly] starting (preview mode)... Processing `hornpipe.ly' Parsing... hornpipe.ly:57:0: error: syntax error, unexpected \score \score { hornpipe.ly:60:38: error: unknown escaped string: `\AvoiceAA' \context Voice = OApartAG \AvoiceAA hornpipe.ly:60:38: error: syntax error, unexpected STRING \context Voice = OApartAG \AvoiceAA /usr/share/lilypond/2.12.2/ly/init.ly:63:66: error: syntax error, unexpected $end (ly:parser-error parser (_ "expected error, but none found")))) error: failed files: "hornpipe.ly" LilyPond [hornpipe.ly] exited with return code 1. I have also tried to process the resulting .ly file in a command terminal and get basically the same error report; GNU LilyPond 2.12.2 Processing `hornpipe.ly' Parsing... hornpipe.ly:57:0: error: syntax error, unexpected \score \score { hornpipe.ly:60:38: error: unknown escaped string: `\AvoiceAA' \context Voice = OApartAG \AvoiceAA hornpipe.ly:60:38: error: syntax error, unexpected STRING \context Voice = OApartAG \AvoiceAA /usr/share/lilypond/2.12.2/ly/init.ly:63:66: error: syntax error, unexpected $end (ly:parser-error parser (_ "expected error, but none found")))) error: failed files: "hornpipe.ly" I do not fully understand much of the Lilypond script so am dependent on programs such as Frescobaldi to help me edit Lilypond files, but somehow it seems MuseScore is not converting its files into a form that Lilypond will accept. I have however saved MuseScore files to xml format and successfully converted them to .ly files with the command musicxml2ly. Log in to post comments ⋅ Categories: Support and bug reports Comments Posted by lasconic on March 15, 2010 - 9:23pm Can you tell which version of MuseScore you are using ? and maybe attach the score you are working on ? Log in to post comments Posted by banjoman on March 16, 2010 - 6:54am MuseScore 0.9.5 on Mandriva Spring20