Comment #4 on issue 3639 by [email protected]: tuplet of a single chord gives a
syntax error
http://code.google.com/p/lilypond/issues/detail?id=3639
In that case, the change in question will pretty certainly be
commit 0dacb8e6afa4c75c781026afb4fa05a4c86cf15a
Merge: 8346054 5195f1f
Author: David Kastrup <[email protected]>
Date: Sat Oct 19 21:36:11 2013 +0200
Merge branch 'issue3618' (early part) into staging
Not sure whether every state in between will perfectly bisect, so
using a merge commit.
Now the previous behavior was a rather fragile state in the parser where it
was not all too well-defined when which rules would trigger for what reason.
The syntax probably took a shortcut reserved for a kind of optional
argument that was not even being used. Now reverting that change is not
really an option as it cut through a lot of putty and shoestring and
brought reasonably predictable and debuggable behavior (and fixed several
ominous bugs I had).
I should be able to bring chords back into the working set here. Any other
noteworthy constructs that might be affected?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
