Re: Lilypond error behaviour

[David Kastrup]

Stephan Neuhaus <address@hidden> writes:

> On 2016-04-19 17:54, Tim Reeves wrote:
>> Maybe they should be called "mortally-wounding" errors? :)
>
> This is an excellent suggestion. Perhaps we could implement that further
> output from Lilypond becomes more and more incoherent as the poison sets
> in? And finally, the pain is too much to bear and Lilypond gives up.

Except that in case of syntax errors, LilyPond "gives up" when it was
going to finish anyway.  If it has further files to process, it will
tackle them first.  Basically it just announces in this manner that it
will quit with non-zero exit code _now_ that it has nothing more to do.

-- 
David Kastrup