Issue 849 in lilypond: Rests should not keep staves alive

[codesite-noreply]

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 printed though it only
contains rests (because of the partial measure, that has to contain a
normal rest and not a full-measure rest):

\version "2.13.4"
\paper{ ragged-right=##t }

\score {
 <<
   \new Staff {
     \partial 16 r16 |  % doesn't work
                        % works if we use s16
     R1*4 | \break R1*4 | \break
     c''1 \bar "|."
   }
   \new Staff {
     \partial 16 c'16 |
     \repeat unfold 4 { c'1 } | \break
     \repeat unfold 4 { c'1 } | \break
     c'1 \bar "|."
   }
 >>

 \layout { \context { \RemoveEmptyStaffContext
     \override VerticalAxisGroup #'remove-first = ##t } }
}


There doesn't seem to be a particular reason to regard normal rests as a
keep-alive interface, other than convenience; Reinhold said
"it's much easier to add rhythmic-grob-interface (which includes normal
rests, but not multi-measure rests) to the keepAliveInterfaces than to
explicitly list all interfaces for rhythmic grobs except the rest-interface"
Please read the discussion on
http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00023.html

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings