Updates:
Status: Verified
Comment #6 on issue 849 by v.villenave: Rests should not keep staves alive
http://code.google.com/p/lilypond/issues/detail?id=849
Works like a charm now. Thanks Carl!
___
bug-lilypond mailing list
bug-lilypond@gnu.or
Comment #5 on issue 849 by x.scheuer: Rests should not keep staves alive
http://code.google.com/p/lilypond/issues/detail?id=849
Great!
Thank you.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Updates:
Status: Fixed
Labels: fixed_2_13_33
Comment #4 on issue 849 by Carl.D.Sorensen: Rests should not keep staves
alive
http://code.google.com/p/lilypond/issues/detail?id=849
Fixed in commit 387bf986cfa362ce3f90dcc7f44a7cc0ab602fb1
___
Updates:
Status: Started
Owner: Carl.D.Sorensen
Comment #3 on issue 849 by Carl.D.Sorensen: Rests should not keep staves
alive
http://code.google.com/p/lilypond/issues/detail?id=849
Yes, this appears to be a trivial change.
___
bug
Comment #2 on issue 849 by x.scheuer: Rests should not keep staves alive
http://code.google.com/p/lilypond/issues/detail?id=849
\RemoveEmptyStaffContext has been reworked recently isn't it?
Couldn't a dev start working on this issue thanks to Nicolas' code or
Reinhold's instructions?
Many thank
Updates:
Owner: ---
Labels: -Priority-Medium -Engraving-nitpick Priority-Low
Comment #1 on issue 849 by percival.music.ca: Rests should not keep staves
alive
http://code.google.com/p/lilypond/issues/detail?id=849
(No comment was entered for this change.)
Attachments:
Status: Accepted
Owner: v.villenave
CC: nicolas.sceaux, reinhold.kainhofer
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 849 by v.villenave: Rests should not keep staves alive
http://code.google.com/p/lilypond/issues/detail?id=849
In the following example, the first staff is p
