From: David Kastrup <dak@gnu.org>
Date: Sun, 28 Aug 2011 19:39:17 +0000 (+0200)
Subject: changes.itely: mention new behavior of #{ ... #}
X-Git-Tag: release/2.15.9-1~5^2~6^2~2
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;ds=sidebyside;h=bf1319672f55dd5c357bd2cd9eef3dda0e599391;p=lilypond.git

changes.itely: mention new behavior of #{ ... #}
---

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index f5e4f151d2..2d8a66eb23 100644
--- a/Documentation/changes.tely
+++ b/Documentation/changes.tely
@@ -61,6 +61,16 @@ which scares away people.
 
 @end ignore
 
+@item
+The construct @code{#@{ @dots{} #@}} can now be used not just for
+constructing sequential music lists, but also for single music events,
+void music expressions, post events, markups (mostly freeing users from
+having to use the @code{markup} macro), markup lists, number
+expressions, context definitions and modifications, and a few other
+things.  If it encloses nothing or only a single music event, it no
+longer returns a sequential music list but rather a void music
+expression or just the music event itself, respectively.
+
 @item
 New command-line option @option{--loglevel=@var{level}} to control how much output
 LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG.