David Kastrup <d...@gnu.org> writes:
> David Kastrup <d...@gnu.org> writes:
>
>> Nicolas Sceaux <nicolas.sceaux.l...@gmail.com> writes:
>>
>>> With lilypond 2.19.3, applying a music function to a bass figure
>>> causes a syntax error. At least until 2.17.24 (I have not tested
>>> later versions), that was not the case.
>>
>> 2.19.0 is ok,
>
> I have to take that back. A binary of mine identifying itself as 2.19.0
> is ok, but that would appear to be from a VERSION before the actual
> release. 2.19.0 itself appears to be flaky already. So looking before
> 2.19.0 now.
ee4b49239c2aeb7ed6b4609391566a276ca0d47c is the first bad commit
commit ee4b49239c2aeb7ed6b4609391566a276ca0d47c
Author: David Kastrup <d...@gnu.org>
Date: Fri Dec 13 06:01:43 2013 +0100
Parser: properly disambiguate pitches from music in function arguments
In many instances, function arguments were parsed greedily without
looking at the function argument predicates first. This did not allow
using subsequent function arguments of type pitch and duration since
they were combined into one music expression.
:040000 040000 b8441604d6f43d10e6748d4f5173f6a0528a448d
b1163d3652d6261b7d7d32181a90eb6421899490 M lily
That's in 2.19.0 and and after 2.17.97.
A somewhat different change from what I expected.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
