Version 2.16.2 and 2.17.95 do not compile correctly
staffs are are not separated as specified.
Sorry for the long annex, but it’s difficult for me to isolate the bug. Suspect
it is in the type of fractions used with the feature “times”.
Mario Bolognani
Via Celimontana, 15
I-00184 Roma
tel. stu
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 lengt
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 Staf
2013/11/4 Steven Weber :
> 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).No matter what I seem to try, the
> multi-measure rest never fills up the entire bar (as seen in the attached
> example.png). I'v
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).No matter what I seem to try, the
multi-measure rest never fills up the entire bar (as seen in the attached
example.png). I've tried overriding the Score.TimeSign
