Re: Lilypond error behaviour

[David Kastrup]

Thomas Morley <address@hidden> writes:

>> just turn on
>> warning-as-error and be done with it.
>
> As I wrote days ago ...

We could implement an option for the maximum number of non-fatal errors
before abort.  People who really do not want to have LilyPond continue
after an error can then set it to zero.

The problem is that there are situations where LilyPond is called with
hundreds of files, and such a hard immediate abort does not leave the
lexer/parser/inputstack in a predictable state, so one would have to
abort processing all files on the command line.

Which may be particularly tricky in connection with the
-djob-count=... option since the control job would presumably have to
kill all other jobs asynchronously which _indeed_ leaves the output
files (including the log files) in undefined state.

-- 
David Kastrup