David Kastrup <[email protected]> writes: > Marnen Laibow-Koser <[email protected]> writes: > >> On Wed, Mar 18, 2020 at 12:18 PM Zone Dremik <[email protected]> wrote: >> >>> It was quite a few years ago that copied this code sample from the >>> LilyPond Notation Reference v2.18.2 webpage: >>> >>> http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables >>> I've compiled hundreds of Lead-Sheets with it, but haven't up-dated >>> Lilypond since 2.18.2 until now. >>> >> >> Right, as David said, it was in fact valid syntax (which I didn’t realize) >> but convert-ly doesn’t know about it. D’oh! So I guess this is under the >> category of “known issues in convert-ly” rather than “broken build”. Sorry >> for the inconvenience! > > More like "should have known issues in convert-ly". Analysis of what > decisions have led there just came up yesterday. There likely is going > to be a fix in 2.20.1 but I cannot yet vouch what.
I may add that this is the kind of thing that happens when everybody decides that they'll wait for "stable" releases rather than trying out betas or prereleases. At some point of time, problems need to get flagged. -- David Kastrup
