On Sat, Jan 10, 2026 at 10:37 AM Carl Sorensen
<[email protected]> wrote:
>
> On Sat, Jan 10, 2026 at 9:45 AM Kieren MacMillan
> <[email protected]> wrote:
> >
> > 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…?
> >
> That snippet does it for bar numbers. Are we sure it's the same
> problem for footers (although I admit it seems very likely)?
>
Further investigation with skyline debugging turned on shows that the
SystemStartBracket skylines do NOT include the tips of the bracket,
which is what allows the collision to happen. You probably already
knew this, but it may be a worthwhile addition to the bug report.
%%% 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
\override SystemStartBracket.show-vertical-skylines = ##t
\override SystemStartBracket.show-horizontal-skylines = ##t
}
}
\new StaffGroup <<
\new Staff { \repeat unfold 6 { c'1 \break } }
\new Staff { R1 R1 \break \repeat unfold 4 { c'1 \break } }
>>
%%%. BUG SNIPPET ENDS
Thanks, and sorry for the noise.
Carl
