Reviewers: Trevor Daniels,
Message:
Second draft,
James
http://codereview.appspot.com/4850051/diff/1/Documentation/notation/staff.itely
File Documentation/notation/staff.itely (right):
http://codereview.appspot.com/4850051/diff/1/Documentation/notation/staff.itely#newcode1304
Documentation/notation/staff.itely:1304: @warning{In this example, the
@code{Voice} context must be explicitly
On 2011/08/09 23:08:15, Trevor Daniels wrote:
@warning{When a @code{Voice} starts with @code{\cueDuring}, as in the
following
example, ... }
Done.
Description:
Doc: NR Warning added to para for cueduring
As per Tracker 1811.
Added @warning{ } around pararaph in cueDuring to alert users to
create explicit contexts in certain cases.
Please review this at http://codereview.appspot.com/4850051/
Affected files:
M Documentation/notation/staff.itely
Index: Documentation/notation/staff.itely
diff --git a/Documentation/notation/staff.itely
b/Documentation/notation/staff.itely
index
b4e471f7b09233c22d62a24c6ffe5cfc72346e7f..06f6089d19cdfeeb2654d47e4a849d21a04c9e9f
100644
--- a/Documentation/notation/staff.itely
+++ b/Documentation/notation/staff.itely
@@ -1301,9 +1301,10 @@ tie-event beam-event tuplet-span-event)}, which
means that only
notes, rests, ties, beams and tuplets are quoted, but not
articulations, dynamic marks, markup etc.
-In this example, the @code{Voice} context must be
-explicitly declared, or else the entire music expression would
-belong to the @code{CueVoice} context.
+@warning{When a @code{Voice} starts with @code{\cueDuring}, as in the
+following example, the @code{Voice} context must be explicitly declared,
+or else the entire music expression would belong to the @code{CueVoice}
+context.}
@lilypond[verbatim,quote]
oboeNotes = \relative c'' {
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
