From: Trevor Daniels Date: Tue, 14 Jul 2009 22:14:07 +0000 (+0100) Subject: Docs: NR Tweak command: can't be used to modify stems, X-Git-Tag: release/2.12.3-1~22 X-Git-Url: https://git.donarmstrong.com/lilypond.git?a=commitdiff_plain;h=789d65a45b89c1fe7ec8ee4e80cca8a687274ea7;p=lilypond.git Docs: NR Tweak command: can't be used to modify stems, beams or accidentals *directly* (cherry picked from commit 48e91a8c2c0aa68f7e55b35016b530ba47b65e35) --- diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely index f94869770e..3e2db8538b 100644 --- a/Documentation/user/changing-defaults.itely +++ b/Documentation/user/changing-defaults.itely @@ -1522,12 +1522,12 @@ and @code{\tweak} may be used to modify any single occurrence of these items. Notably the @code{\tweak} command cannot be used to modify stems, -beams or accidentals, since these are generated later by note heads, -rather than by music elements in the input stream. Nor can a -@code{\tweak} command be used to modify clefs or time signatures, -since these become separated from any preceding @code{\tweak} -command in the input stream by the automatic insertion of extra -elements required to specify the context. +beams or accidentals directly, since these are generated later by +note heads, rather than by music elements in the input stream. +Nor can a @code{\tweak} command be used to modify clefs or time +signatures, since these become separated from any preceding +@code{\tweak} command in the input stream by the automatic +insertion of extra elements required to specify the context. But the @code{\tweak} command can be used as an alternative to the @code{\override} command to modify those notational elements