From: colinpkcampbell@gmail.com Date: Fri, 22 Jul 2011 01:47:04 +0000 (-0600) Subject: DOC: fix NR 1.6.3 Formatting Cue Notes X-Git-Tag: release/2.15.9-1~48^2 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=2d30bf30c3af6e7c4f1d158ec095c67450adea79;p=lilypond.git DOC: fix NR 1.6.3 Formatting Cue Notes Moves comment about explicitly creating a Voice, to the proper example. --- diff --git a/Documentation/notation/staff.itely b/Documentation/notation/staff.itely index 5344ab2b86..b4e471f7b0 100644 --- a/Documentation/notation/staff.itely +++ b/Documentation/notation/staff.itely @@ -1292,9 +1292,7 @@ oboeNotes = \relative c'' { @end lilypond @noindent -In the above example, the @code{Voice} context had to be -explicitly declared, or else the entire music expression would -belong to the @code{CueVoice} context. + It is possible to adjust which aspects of the music are quoted with @code{\cueDuring} by setting the @code{quotedCueEventTypes} @@ -1303,6 +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. + @lilypond[verbatim,quote] oboeNotes = \relative c'' { r2 r8 d16(\f f e g f a)