lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with make on a commit *after* Davids last '\pushAtTag' commi


From: David Kastrup
Subject: Re: Problem with make on a commit *after* Davids last '\pushAtTag' commit - 264022bd6ebfed3220c0272d2c4a1c8ef9db4028
Date: Thu, 22 Sep 2011 14:57:16 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

David Kastrup <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>
>> Peekay Ex <address@hidden> writes:
>>
>>> Hello,
>>>
>>> I'm getting the following error when I tried to 'make' this morning.
>>>
>>> --snip--
>>>
>>> /home/jlowe/lilypond-git/ly/string-tunings-init.ly:128:0: error:
>>> syntax error, unexpected MUSIC_FUNCTION
>>
>> Am bisecting right now, this is likely caused by a change of mine I
>> considered totally trivial.
>>
>> I know I know.
>
> Reverted.  I have no clue whatsoever what could possibly cause this
> error, probably something related to parser lookahead at inconvenient
> times.
>
> It is always the trivial things that I mess up.

Appalling oversight.

composite_music could also have been prefix_composite_music, so
replacing it with closed_music is not an option.  I have to sort
prefix_composite_music out into its components and try to come up with
something that is at least as permissive as what we started with.

And put up a patch review for the next "trivial" change I do to make
somebody happy.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]