[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-devel
Subject:    Re: NR: Document \remove "Keep_alive_together_engraver" (issue 318580043 by git@ursliska.de)
From:       git () ursliska ! de
Date:       2017-02-17 7:08:20
Message-ID: 001a114f87b4274ee50548b494a0 () google ! com
[Download RAW message or body]

Reviewers: lemzwerg,

Message:
On 2017/02/17 05:38:44, lemzwerg wrote:
> ...
Please use two spaces after a full stop that closes a sentence.

Sorry, missed that one. Fixed but without new patch set.



Description:
NR: Document \remove "Keep_alive_together_engraver"

Please review this at https://codereview.appspot.com/318580043/

Affected files (+43, -1 lines):
   M Documentation/notation/staff.itely


Index: Documentation/notation/staff.itely
diff --git a/Documentation/notation/staff.itely  
b/Documentation/notation/staff.itely
index  
d7ed3e6738b55b9cb8ac7bbc3cc496625c8d0eaf..1526ce18b5f288c1d91f713d999d2d69b37bd3f3  
100644
--- a/Documentation/notation/staff.itely
+++ b/Documentation/notation/staff.itely
@@ -785,6 +785,49 @@ elements.}
  >>
  @end lilypond

+By default any empty staff can be frenched, but sometimes staff groups
+are linked and should only be hidden together when @emph{all} staves are
+empty at the same time. This behaviour is the default for @code{PianoStaff}
+where empty staves are usually continued.  The
+@code{Keep_alive_together_engraver} which is responsible for this can be
+removed from the @code{PianoStaff} context to allow individual staves to
+be frenched.  This is for example useful in complex piano music that
+features sections with two or more staves.
+
+@lilypond[verbatim,quote,ragged-right]
+\layout {
+  \context {
+    \Staff
+    \RemoveEmptyStaves
+  }
+  \context {
+    \PianoStaff
+    \remove "Keep_alive_together_engraver"
+  }
+}
+
+\relative <<
+  \new PianoStaff <<
+    \new Staff {
+      e'4 f g a \break
+      b1 \break
+      a4 b c2
+    }
+    \new Staff {
+      c,4 d e f \break
+      R1 \break
+      f4 g c,2
+    }
+    \new Staff {
+      \clef bass
+      c,4 d e f \break
+      g1 \break
+      f4 g c,2
+    }
+  >>
+>>
+@end lilypond
+
  @cindex ossia

  @noindent
@@ -1507,4 +1550,3 @@ between @code{Voice} and @code{CueVoice} contexts.   
When using
  @code{\cueDuringWithClef} or @code{\transposedCueDuring} the extra
  argument required for each case must come after the quote and the
  direction.
-



_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
[prev in list] [next in list] [prev in thread] [next in thread]