From: Trevor Daniels Date: Sat, 13 Apr 2013 17:35:55 +0000 (+0100) Subject: Add warning about using \relative with tagged music (3253) X-Git-Tag: release/2.17.17-1~27^2~6 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=ee0ef98a35634718033d505deb8a355e05513d6a;p=lilypond.git Add warning about using \relative with tagged music (3253) - add warning as a known issue - remove earlier ignored known issue --- diff --git a/Documentation/notation/input.itely b/Documentation/notation/input.itely index e48597557e..2debffd336 100644 --- a/Documentation/notation/input.itely +++ b/Documentation/notation/input.itely @@ -2242,16 +2242,14 @@ Notation Reference: @ref{Automatic part combining}, @ref{Including LilyPond files}. -@ignore -@c This warning is more general than this placement implies. -@c Rests are not merged whether or not they come from tagged sections. -@c Should be deleted? -td - @knownissues -Multiple rests are not merged if you create a score with more -than one tagged section at the same place. - -@end ignore +Calling @code{\relative} on a music expression obtained by filtering +music through @code{\keepWithTag} or @code{\removeWithTag} might cause +the octave relations to change, as only the pitches actually +remaining in the filtered expression will be considered. Applying +@code{\relative} first, before @code{\keepWithTag} or +@code{\removeWithTag}, avoids this danger as @code{\relative} then +acts on all the pitches as-input. @node Using global settings