Hi Carl,
> The ideal bug repot would show a collision without a warning for a overfull
> page.
>
> The collisions I have seen on this came with an overfull page warning, which
> shows me that Lilypond knows about he collision but can't avoid it because
> the systems take up too much space on the page because of bad height
> estimates during linebreaking and pagebreaking calculations.
>
> It would be nice to know if the collision occurs without an overfull page.
I believe the bug example I put earlier in this thread does that…?
%%% BUG (?) SNIPPET BEGINS
\version "2.25.24"
\layout {
\context {
\Score
\RemoveAllEmptyStaves
\override BarNumber.padding = 0.5
\override BarNumber.self-alignment-X = #0
\override BarNumber.direction = #DOWN
}
}
\new StaffGroup <<
\new Staff { \repeat unfold 6 { c'1 \break } }
\new Staff { R1 R1 \break \repeat unfold 4 { c'1 \break } }
>>
%%% BUG (?) SNIPPET ENDS
Cheers,
Kieren.
__________________________________________________
My work day may look different than your work day. Please do not feel obligated
to read or respond to this email outside of your normal working hours.
