From: David Kastrup <dak@gnu.org>
Date: Sun, 7 Aug 2016 11:57:25 +0000 (+0200)
Subject: Issue 4954/2: Changes entries for \= and in-chord slurs
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=0bab8fec496686ed5d3a086085fa068c41974c42;p=lilypond.git

Issue 4954/2: Changes entries for \= and in-chord slurs
---

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index fb1a77f633..c9315d59da 100644
--- a/Documentation/changes.tely
+++ b/Documentation/changes.tely
@@ -61,6 +61,25 @@ which scares away people.
 
 @end ignore
 
+@item
+Slurs and phrasing slurs may now be started from individual notes
+in a chord.  Several simultanous slurs per @code{Voice} need to be
+distinguished by @code{spanner-id} setting.
+
+@item
+The music and grob property @code{spanner-id} for distinguishing
+simultaneous slurs and phrasing slurs has been changed from a
+string to a @q{key}, a non-negative integer or symbol.
+
+@item
+There is a new command @code{\=} for specifying the
+@code{spanner-id} for simultaneous slurs and phrasing slurs.
+@lilypond[verbatim,quote]
+\fixed c' {
+  <c~ f\=1( g\=2( >2 <c e\=1) a\=2) >
+}
+@end lilypond
+
 @item
 Blocks introduced with @code{\header} can be stored in variables
 and used as arguments to music and scheme functions and as the