[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
Sharon Rosner |
Subject: |
Re: Lilypond error behaviour |
Date: |
Tue, 19 Apr 2016 23:33:01 +0200 |
> It would be a little less futile, if people would try harder to read
> and to understand what was written and think about it.
> Really no reason for a flame-war.
That was not my intention, and I tried really hard to think about this problem.
Call me slow :-)
Sharon
- Re: Lilypond error behaviour, (continued)
- 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, 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 <=
- Re: Lilypond error behaviour, Noeck, 2016/04/16
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