[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
David Kastrup |
Subject: |
Re: Lilypond error behaviour |
Date: |
Sun, 17 Apr 2016 22:16:32 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Noeck <address@hidden> writes:
> These two are often similar but not always.
> IMHO, it would make sense to consider both and have 3 categories:
> - warning: user, please look at this
> - error: this is severe, there is something definitely wrong, but
> Lilypond did its very best to keep running
> - fatal error: this is severe and Lilypond could not rescue the
> situation, nothing was produced
We are not talking about "nothing was produced" since LilyPond can't
change the past. The demand rather boils down to "if LilyPond has
already successfully produced anything, that should not be left
available and the PDF should not be completed properly."
--
David Kastrup
- Re: Lilypond error behaviour, (continued)
- 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
- Re: Lilypond error behaviour, Kieren MacMillan, 2016/04/17
- Re: Lilypond error behaviour, David Kastrup, 2016/04/17
- Re: Lilypond error behaviour, Kieren MacMillan, 2016/04/17
- Re: Lilypond error behaviour, Noeck, 2016/04/17
- Re: Lilypond error behaviour,
David Kastrup <=
- Re: Lilypond error behaviour, Tim McNamara, 2016/04/17
- Re: Lilypond error behaviour, Noeck, 2016/04/18
- Re: Lilypond error behaviour, Thomas Morley, 2016/04/17
- Re: Lilypond error behaviour, Thomas Morley, 2016/04/18
- Re: Lilypond error behaviour, Noeck, 2016/04/18
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/17
- Re: Lilypond error behaviour, David Kastrup, 2016/04/17
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/18
- Re: Lilypond error behaviour, mskala, 2016/04/18
- Re: Lilypond error behaviour, David Wright, 2016/04/18