Laziness. The movement I'm typesetting is 600+ measures long with tons of time changes, and only 15 measures of that are split. That's why LP allows this kind of construct in the first place, no? Because we still don't have a good way to say "skip the next 500 measures, regardless of their length."
--Steven -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Eluze Sent: Monday, November 04, 2013 4:05 PM To: [email protected]; [email protected] Subject: Re: Multi-measure rests before a new temporary staff is added Steven Weber wrote > Lilypond 2.17.29, Windows 7. > > I'm typesetting a piece where the part splits after a multi-measure rest > (and a forced line break). why not use the "usual" construct that defines the staff group from the begin and removes parts if they're _empty_: \score{ \new StaffGroup \with { \RemoveEmptyStaves \override VerticalAxisGroup #'remove-first = ##t } << \new Staff { \compressFullBarRests \override MultiMeasureRest.expand-limit = #1 \new Voice \repeat unfold 5 { c4 d e f | } R1 *5 | \break \repeat unfold 5 { c4 d e f | } } \new Staff { \clef bass \time 4/4 \colorContext blue \key f \major s1 *10 \repeat unfold 5 { c,4 d, e, f, | } } >> } Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Multi-measure-rests-before-a-new-tempo rary-staff-is-added-tp153390p153395.html Sent from the Bugs mailing list archive at Nabble.com. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
