Fix 456: Also check for laissez-vibrer events attached to single heads inside a chord

[lilypond.git] / Documentation / changes.tely

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index fcfd6ed68b71fd8d060ae99f6436d203196de41e..70544254f84e832faa41e57d1e4e6d44c6e66a82 100644 (file)
--- a/Documentation/changes.tely
+++ b/Documentation/changes.tely
@@ -61,6 +61,26 @@ which scares away people.
 
 @end ignore
 
+@item
+There is a new @code{define-scheme-function} command in analogy to
+@code{define-music-function} which can be used to define functions
+evaluating to Scheme expressions while accepting arguments in Lilypond
+syntax.
+
+@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.
+
 @item
 @code{\set \once} now correctly resets the property value to the previous value.
 @lilypond[fragment,quote,relative=2]