...and I just realized that I can use \once for that purpose! Thank you for helping me through this!
On Tue, Dec 3, 2024 at 4:25 PM Eric Benson <ebseat...@gmail.com> wrote: > OK, I see the problem. Since my page breaks are nearly always explicit, I > could get the effect I need if there was a way to say "change the rule for > this upcoming break, but then change it back immediately after". Otherwise > I have to put the undo setting somewhere after the beginning of the first > line on the new page, but not after the beginning of the second line on the > new page. If I could do both at the same place I could just combine them > with my explicit \pageBreak. > > On Tue, Dec 3, 2024 at 2:27 PM David Kastrup <d...@gnu.org> wrote: > >> Eric Benson <ebseat...@gmail.com> writes: >> >> >> On Fri, Nov 29, 2024 at 1:13 PM Eric Benson <ebseat...@gmail.com> >> wrote: >> >> >> >>> I'm making lead sheets, where, unlike common practice, the key >> signature >> >>> and clef are not usually shown at the beginning of each line. LilyPond >> >>> makes this easy to control, with >> >>> >> >>> \override Score.Clef.break-visibility = #all-invisible >> >>> >> >>> and >> >>> >> >>> \override Score.KeySignature.break-visibility = #all-invisible >> >>> >> >>> That works great. Most lead sheets are only a single page, but when >> >>> they are longer I like to put the clef and key signature and clef at >> >>> the beginning of the first line of each page. I'm doing that now by >> >>> un-overriding and re-overriding these settings around page breaks, >> >>> but that is somewhat messy and fragile. I'd like to find a better >> >>> way to do this. Does anyone know of a way? Otherwise, I guess this >> >>> is a feature request! >> >> >> > >> > Any thoughts? Anyone? >> >> LilyPond breaks lines, and breaks pages after having established how the >> lines look. >> >> So this is not something that a "feature request" can do. The best you >> can hope for is telling LilyPond where it can break the page including >> key signatures and so on and forbid it to break page anywhere else. >> >> It can even be a range of measures that you are sure will take more than >> 1 line and less than 2. >> >> -- >> David Kastrup >> >
