Recently we experienced strange crashes in our Lilypond scores that could only be avoided by randomly changing the order of some function calls.
Now I sat down and pinned it down quite narrowly:
If I use your wonderful \shape function and afterwards override any property of the same grob it causes Lilypond to crash while 'creating systems'.
Attached you'll find a file with detailed observations.
My impression is that your function somehow messes up with the grob's variable/pointer or whatever, making a copy and not telling Lilypond or such kind of thing.
Anyone an idea what could be wrong here?
It doesn't make the function unusable (not at all), but it can cause very dubious errors that might be very hard to track (depending on the situation).
Best
Urs
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
shapeCanCrash.ly