Am Mittwoch, dem 09.12.2020 um 22:16 +0100 schrieb Mats Bengtsson:
> Hi,
>
> I just tried a larger score in 2.21.81 and found a regression bug
> compared to 2.20.0, that's illustrated in the following example:
>
> \fixed c'{
> e4 8. 16 \afterGrace e2 {d16 e } | % Works fine
> f4 4 r2 |
> e4 8. 16 \afterGrace 2 {d16 e } | % Breaks in 2.21.81, works fine in 2.20.0
> f4 4 r2 |
> }My gut feeling proved right here that this breakage is the result of an intentional change of behavior, bisection leads to: 027538606b016afb643555d654cefaee94dfb424 is the first bad commit commit 027538606b016afb643555d654cefaee94dfb424 Author: David Kastrup <[email protected]> Date: Wed May 23 19:08:31 2018 +0200 Issue 5327/4: Let \afterGrace and \scaleDurations take a scale That's more versatile than allowing just a fraction as a pair as previously. ly/music-functions-init.ly | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) So in \afterGrace 2, the argument is taken as a scale rather than music in 2.20. I don't see a way to fix this, and I'm not sure we should because the syntax is indeed ambiguous... Jonas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
