[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
mskala |
Subject: |
Re: Lilypond error behaviour |
Date: |
Sun, 17 Apr 2016 06:59:53 -0500 (CDT) |
User-agent: |
Alpine 2.20 (LNX 67 2015-01-07) |
On Sun, 17 Apr 2016, Urs Liska wrote:
> No, of course not. If LilyPond is able to "recover" (as Andrew put it) it
> should of course do so. But it should not report a "fatal error" and a
> "failed file" then.
I think the whole thing comes down to something very simple which
ought to go without saying, but evidently needs to be said after all:
Lilypond should not lie.
--
Matthew Skala
address@hidden People before principles.
http://ansuz.sooke.bc.ca/
- Re: Lilypond error behaviour, (continued)
- 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 <=
- 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, 2016/04/17
- 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