[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
mskala |
Subject: |
Re: Lilypond error behaviour |
Date: |
Mon, 18 Apr 2016 12:49:25 -0500 (CDT) |
User-agent: |
Alpine 2.20 (LNX 67 2015-01-07) |
On Mon, 18 Apr 2016, David Kastrup wrote:
> address@hidden writes:
> > If compiling the file has failed to such a degree that we are choosing
> > to call it a "fatal error," that means the PDF is *not* suitable for
> > further use. Conversely, if you think the generated PDF is still
> > useful, then don't call what happened a "fatal error" - it must have
> > really been a warning.
>
> With that definition, any error that does not terminally destroy the
> computer is not a fatal error since otherwise you can still debug the
> problem.
That is not true.
--
Matthew Skala
address@hidden People before principles.
http://ansuz.sooke.bc.ca/
- Re: Lilypond error behaviour, (continued)
- 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
- Re: Lilypond error behaviour, mskala, 2016/04/18
- Re: Lilypond error behaviour, David Kastrup, 2016/04/18
- Re: Lilypond error behaviour,
mskala <=
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/18
- Re: Lilypond error behaviour, Anthonys Lists, 2016/04/18
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/18
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/18
- Re: Lilypond error behaviour, Noeck, 2016/04/19
- Re: Lilypond error behaviour, mskala, 2016/04/19
- Re: Lilypond error behaviour, Thomas Morley, 2016/04/19
- Re: Lilypond error behaviour, mskala, 2016/04/19
- Re: Lilypond error behaviour, David Kastrup, 2016/04/19
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/19