lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Doc: correct warning re tied chords (2690) (issue 6427058)


From: tdanielsmusic
Subject: Doc: correct warning re tied chords (2690) (issue 6427058)
Date: Fri, 27 Jul 2012 07:30:38 +0000

Reviewers: ,

Message:
Pushed to staging as
3573a92d92728dc8d6452e5cd3cfba73e49e6990
Closing

Description:
Doc: correct warning re tied chords (2690)

Restore original wording which restricts this
warning to the control points of ties

Please review this at http://codereview.appspot.com/6427058/

Affected files:
  M Documentation/notation/changing-defaults.itely


Index: Documentation/notation/changing-defaults.itely
diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely index b0cfac035c62d55e58b80679bc4491566b9fbbb4..ae59d06ee8214b17aedbf26f4cee78828b0a9e69 100644
--- a/Documentation/notation/changing-defaults.itely
+++ b/Documentation/notation/changing-defaults.itely
@@ -2228,9 +2228,9 @@ Extending LilyPond:
 @cindex tweaking control points
 @cindex control points, tweaking

-The @code{\tweak} command will apply to only the first of several
-generated ties in a chord.
-
+The @code{\tweak} command cannot be used to modify the control
+points of just one of several ties in a chord, other than the first
+one encountered in the input file.

 @node set versus override
 @subsection @code{\set} vs. @code{\override}





reply via email to

[Prev in Thread] Current Thread [Next in Thread]