[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
Urs Liska |
Subject: |
Re: Lilypond error behaviour |
Date: |
Sun, 17 Apr 2016 11:08:04 +0200 |
User-agent: |
K-9 Mail for Android |
Am 17. April 2016 10:51:34 MESZ, schrieb David Kastrup <address@hidden>:
>Urs Liska <address@hidden> writes:
>
>> Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup <address@hidden>:
>>
>>>A warning is appropriate for something which is not an error: namely
>>>LilyPond has a well-specified task but the results will not likely
>>>make sense. LilyPond does not return an error code for a warning.
>>
>> Well, then let LilyPond report an error when it encounters one. But
>> only then a "fatal" one when it actually forces LilyPond to stop.
>
>For any _correct_ input, LilyPond is eventually forced to stop.
This is the point where I have to say you are talking bullshit, deliberately
(?) and arbitrarily flipping around everyone's words and intentions. It doesn't
make sense to continue with that thread.
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 <=
- 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, 2016/04/17