[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
Noeck |
Subject: |
Re: Lilypond error behaviour |
Date: |
Sat, 16 Apr 2016 11:11:08 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
The wording 'fatal error' is perhaps a bit strong if a pdf is still
produced. But I always liked it (especially as a beginner) that LilyPond
tries hard to keep on going and produces output if it can, despite
(partially) severe input errors on the user side.
>From my experience, the return code indicates correcty whether there
were errors or not.
Cheers,
Joram
- Re: Lilypond error behaviour, (continued)
- 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, 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, 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 <=
Re: Lilypond error behaviour, Andrew Bernard, 2016/04/17
- Re: Lilypond error behaviour, David Kastrup, 2016/04/17
- Re: Lilypond error behaviour, Urs Liska, 2016/04/17
- Re: Lilypond error behaviour, David Kastrup, 2016/04/17
- Re: Lilypond error behaviour, Urs Liska, 2016/04/17
- Re: Lilypond error behaviour, David Kastrup, 2016/04/17
- Re: Lilypond error behaviour, Urs Liska, 2016/04/17
- Re: Lilypond error behaviour, mskala, 2016/04/17
- Re: Lilypond error behaviour, Thomas Morley, 2016/04/17
- Re: Lilypond error behaviour, David Kastrup, 2016/04/17