Re: Lilypond error behaviour

[Stephan Neuhaus]

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.

Something like this:

$ lilypond playground/error.ly
GNU LilyPond 2.19.37
Processing `/tmp/lyp/wrappers/error.ly'
Happily parsing...
/Users/sharon/playground/error.ly:1:3: aargh! they got me, the bastards!
/Users/sharon/playground/error.ly:1:3 error: unrecognized string, not in
text script or \lyricmode
{
  bork }
/tmp/lyp/wrappers/error.ly:1: warning: no ... \version ... statement
found, please ... oh god, do I have to go through with this?
/tmp/lyp/wrappers/error.ly:1: dammit, add

\version "2.19.37"

for future compa... ti... bility
Interpreting ... music... though ... it's ... hard ...
Ah crap, I've had it. Tell George he can keep the horse.
Fly, you fools!
$

Fun,

Stephan
-- 
GPG key ID 4BDA81D3
    fingerprint 5F88 399F 8811 72BE B36A  FC93 4D13 FCB2 4BDA 81D3