carl.d.soren...@gmail.com writes:
> On 2018/04/25 12:22:18, knupero wrote:
>
>
>> @Everyone: I won't bother you here any longer.
>
> Knut,
>
> It's not a bother.
>
> But it's important to recognize that the parser is a difficult system to
> work with, and we've had lots of problems over the years
On 2018/04/25 12:22:18, knupero wrote:
@Everyone: I won't bother you here any longer.
Knut,
It's not a bother.
But it's important to recognize that the parser is a difficult system to
work with, and we've had lots of problems over the years with lookahead
not being handled properly. So the
On 2018/04/25 12:22:18, knupero wrote:
> I don't see the point in starting a formal review after this has
already been
> discussed on the mailing list.
I was hoping, apparently in vain, that the formal process would lead
to a more
reasonable discussion.
You make it appear like "reasonabl
I don't see the point in starting a formal review after this has
already been
discussed on the mailing list.
I was hoping, apparently in vain, that the formal process would lead to
a more reasonable discussion. Apparently, however, this process also
invites speculation about the amount of work
On 2018/04/25 08:36:05, dak wrote:
We don't state "please don't use that syntax in the following way or
LilyPond
will be silently confused into producing nonsense" in other respects
so it is
irrelevant that LilyPond can parse _some_ input correctly with that
change and
will "only" get conf
On 2018/04/25 06:33:19, knupero wrote:
Please test & review the proposed syntax change.
I don't see the point in starting a formal review after this has already
been discussed on the mailing list. In particular since this differs
from your originally proposed patch (where you did not switch to
Reviewers: ,
Message:
Please test & review the proposed syntax change.
Description:
Syntax: lyric_mode_music might be a MUSIC_FUNCTION
With this patch, all four scores in the lilypond
source below use a valid syntax and produce correct
output.
Without this patch only the first two scores use
a
