1 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
2 @setfilename lilypond-changes.info
3 @settitle LilyPond Changes
8 @macro inputfileref{DIR,NAME}
9 @uref{../../\DIR\/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
11 @macro usermanref{NAME}
12 @inforef{\NAME\,,../user/lilypond/lilypond}@c
17 @macro inputfileref{DIR,NAME}
20 @macro usermanref{NAME}
21 See user manual, \NAME\
25 @macro textanchor{NAME}
32 @documentencoding utf-8
39 @top New features in 2.16 since 2.14
41 @allowcodebreaks false
49 * add new items at the top
51 * only show verbatim input for syntax/input changes
53 * try to be as brief possible in those cases
55 * don't try to provide real-world examples, they often get too big,
56 which scares away people.
58 * Write complete sentences.
60 * only show user-visible changes.
64 Scheme expressions inside of embedded Lilypond (@code{#@{@dots{}#@}})
65 are now executed in lexical closure of the surrounding Scheme code.
66 @code{$} is no longer special in embedded Lilypond. It can be used
67 unconditionally in Lilypond code for immediate evaluation, similar to
68 how @code{ly:export} could previously be used. @code{ly:export} has
69 been removed. As a consequence, @code{#} is now free to delay
70 evaluation of its argument until the parser actually reduces the
71 containing expression, greatly reducing the potential for premature
75 The @code{\markuplines} command has been renamed to @code{\markuplist}
76 for a better match with its semantics and general Lilypond
80 The interface for specifying string tunings in tablature has been
81 simplified considerably.
84 Beams can now have their slopes preserved over line breaks.
85 @lilypond[fragment,quote,relative=2]
86 \override Beam #'breakable = ##t
87 a8[ b c d e f g \bar "" \break f e d c b a]
88 \once \override Beam #'positions = #beam::align-with-broken-parts
89 a8[ b c d e f g \bar "" \break f e d c b a]
90 \once \override Beam #'positions = #beam::slope-like-broken-parts
91 a8[ b c d e f g \bar "" \break f e d c b a]
93 To do this, several callback functions are now deprecated.
95 @item @code{ly:beam::calc-least-squares-positions}
96 @item @code{ly:beam::slope-damping}
97 @item @code{ly:beam::shift-region-to-valid}
99 Furthermore, @code{ly:beam::quanting} now takes an additional argument
100 to help calculations over line breaks. All of these functions are now
101 automatically called when setting the @code{positions} parameter.
104 In function arguments music, markups and Scheme expressions (as well
105 as several other syntactic entities) have become mostly
106 interchangeable and are told apart only by evaluating the respective
110 Music functions (and their close relatives) can now be defined with
114 For defining commands executed only for their side-effects,
115 @code{define-void-function} is now available.
118 There is a new @code{define-event-function} command in analogy to
119 @code{define-music-function} that can be used for defining music
120 functions acting as events without requiring a direction specifier
121 (@code{-}, @code{^}, or @code{_}) placed before them.
122 @lilypond[quote,verbatim,raggedright]
123 dyn=#(define-event-function (parser location arg) (markup?)
124 (make-dynamic-script arg))
125 \relative c' { c\dyn pfsss }
129 A list of ASCII aliases for special characters can be included.
130 @lilypond[quote,verbatim]
132 #(include-special-characters)
134 \markup "• † ©right; &OE; &ss; ¶"
138 There is a new @code{define-scheme-function} command in analogy to
139 @code{define-music-function} that can be used to define functions
140 evaluating to Scheme expressions while accepting arguments in Lilypond
144 The construct @code{#@{ @dots{} #@}} can now be used not just for
145 constructing sequential music lists, but also for single music events,
146 void music expressions, post events, markups (mostly freeing users from
147 having to use the @code{markup} macro), markup lists, number
148 expressions, context definitions and modifications, and a few other
149 things. If it encloses nothing or only a single music event, it no
150 longer returns a sequential music list but rather a void music
151 expression or just the music event itself, respectively.
154 New command-line option @option{--loglevel=@var{level}} to control how much output
155 LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG.
158 @code{\set \once} now correctly resets the property value to the previous value.
159 @lilypond[fragment,quote,relative=2]
160 \set fingeringOrientations = #'(left)
162 \once \set fingeringOrientations = #'(right)
169 The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now
170 automatically broken if a different direction is explicitly given.
171 @lilypond[fragment,quote,relative=2]
177 Appoggiaturas and acciaccaturas now also work inside a slur, not only inside
178 a phrasing slur. Also, a function @code{\slashedGrace} was added that does
179 does not use a slur from the acciaccatura note.
180 @lilypond[fragment,quote,relative=2]
181 c4( \appoggiatura e8 d4 \acciaccatura e8 d4 \slashedGrace e8 c4)
186 To suppress the line on a crescendo text spanner (and other similar spanners),
187 LilyPond now fully supports the @code{#'style = #'none} property.
188 @lilypond[fragment,quote,relative=2]
189 \override DynamicTextSpanner #'style = #'none
194 LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz!
197 Glissandi can now span multiple lines.
202 For older news, go to
203 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/},
204 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html},
205 or @uref{../,go back} to the Documentation index.