Re: minimumVerticalExtent.ly again

[Werner LEMBERG]

> > I just want to report that my bug report
> > w.r.t. minimumVerticalExtent also affects lilypond 2.3.11.  This
> > is a really serious issue IMHO.  For convenience, I'm repeating it
> > here.
> 
> This is not a bug, but rather an unintended consequence of
> compatibility feature.  minimumVerticalExtent is syntactic sugar for
> 
>  \override VerticalAxisGroup #'minimum-Y-extent = #...
> 
> which dates from the time that these properties could not be set
> with \override.
> 
> "Fixing" this "bug" actually implies significant brainsurgery on how
> property values are computed.  I don't consider it a priority
> problem.

???  *You* told me in a previous mail to use the minimumVerticalExtent
property to solve my problem!  Anyway, I replaced

  \set Staff.minimumVerticalExtent = #'(-10 . 10)

with

  \override VerticalAxisGroup #'minimum-Y-extent = #'(-10 . 10)

in minimumVerticalExtent.ly and I get

   warning: Can't find property type-check for `minimum-Y-Extent'
            (backend-type?).  Perhaps you made a typing error?
   warning: Doing assignment anyway.

In the output, now there is no minimum vertical extent at all in any
lines.

This looks like another bug, or am I doing something wrong?  I really
need a fix for this, or my full score looks awfully bad.


    Werner