Hi Knute, Oh great! I don't really understand how that all works with the vectors and things, but this worked a treat :-) Thank you again 🥰
Brent. On Sat, 5 Jul 2025 at 01:51, Knute Snortum <[email protected]> wrote: > On Fri, Jul 4, 2025 at 3:52 PM Brent Annable <[email protected]> > wrote: > >> Hey Knute, >> >> Thanks! Interesting epilogue: Lilypond automatically placed this >> particular key change at the end of a line, and then all the key signatures >> at the beginning of the next system are kicked off the staves to the left: >> >> ... > >> I can force a \noBreak at that point, but the result is significantly >> less appealing. Is there any way to fix this flow-on effect? >> > > I think I misread your original post, so here is a better solution with > more entries in the vector. The entire vector with entries in their > default order is below so you can add or change entries as you like: > > %%% > \version "2.24.4" > > \score { > \new StaffGroup << > \new Staff { > \relative c'' { > \hide Staff.BarLine > \key bes \major > c4 c c c | c c c c > } > } > \new Staff { > \relative c'' { > \hide Staff.BarLine > \key bes \major > c1 > \once \override Score.BreakAlignment.break-align-orders = > #(make-vector 3 '(clef > key-signature > staff-bar > time-signature > )) > \key es \major \break > c4 c c c > } > } > >> > } > > %% Entire vector in default order: > % > % #(make-vector 3 '(left-edge > % staff-ellipsis > % cue-end-clef > % ambitus > % breathing-sign > % signum-repetitionis > % clef > % cue-clef > % staff-bar > % key-cancellation > % key-signature > % time-signature > % custos)) > > %%% > > -- > Knute Snortum > >
