[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
Sharon Rosner |
Subject: |
Re: Lilypond error behaviour |
Date: |
Tue, 19 Apr 2016 23:30:05 +0200 |
> More exactly, LilyPond's task is to read a LilyPond input file and
> process its contained expression according to the setting of hook
> variables (those may do something other than typesetting, for example
> converting to a MusicXML expression and writing it out again). Some
> processing may result in files being generated (including PDF files).
> But the generation of PDF files is a side effect. It does not have a
> relation to the occurence of errors.
OK, I think I finally get it. But then why are the errors classified as
“fatal”? Is it only so that the exit code would be non-zero? Is this the
difference between fatal and non-fatal errors? If so, maybe a better term could
be used?
Sharon
- Re: Lilypond error behaviour, (continued)
- Re: Lilypond error behaviour, Simon Albrecht, 2016/04/17
- Re: Lilypond error behaviour, Urs Liska, 2016/04/17
- Re: Lilypond error behaviour, Stephan Neuhaus, 2016/04/18
- Re: Lilypond error behaviour, David Wright, 2016/04/18
- Re: Lilypond error behaviour, Stephan Neuhaus, 2016/04/19
- Re: Lilypond error behaviour, David Wright, 2016/04/19
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/19
- Re: Lilypond error behaviour, David Kastrup, 2016/04/19
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/19
- Re: Lilypond error behaviour, David Kastrup, 2016/04/19
- Re: Lilypond error behaviour,
Sharon Rosner <=
- Re: Lilypond error behaviour, David Kastrup, 2016/04/19
- Re: Lilypond error behaviour, Thomas Morley, 2016/04/19
- Re: Lilypond error behaviour, David Kastrup, 2016/04/19
- Re: Lilypond error behaviour, Thomas Morley, 2016/04/19
- Re: Lilypond error behaviour, David Kastrup, 2016/04/19
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/19
- Re: Lilypond error behaviour, Noeck, 2016/04/16
Re: Lilypond error behaviour, Andrew Bernard, 2016/04/17