use trap to remove tmp directory on failure to avoid hiding mpost

[lilypond.git] / Documentation / changes.tely

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index b3fe430955eb778f9f8f932c832d8945d433ec8a..632ce2042f9b647385dd92ce8d4c13e25eea80c6 100644 (file)
--- a/Documentation/changes.tely
+++ b/Documentation/changes.tely
@@ -61,6 +61,17 @@ which scares away people.
 
 @end ignore
 
+@item
+Use of @code{\tempo} specifications in @code{\midi} blocks (removed in
+2.9.16 in favor of explicit @code{tempoWholesPerMinute} settings) has
+seen a revival: now any kind of property-setting music is turned into
+context definitions within of output specifications, allowing for
+declarations like
+@example
+\layout @{ \accidentalStyle modern @}
+\midi @{ \tempo 4. = 66 @}
+@end example
+
 @item
 The LilyPond G clef has been redesigned - upper loop is now more balanced,
 bottom crook sticks out less and the "spine" (main vertical line) is more
@@ -127,33 +138,43 @@ the Scheme function @code{event-chord-wrap!}  converts to the old
 representation; using one of those might be easiest for keeping legacy
 code operative.
 
-The advantages of making input and music match more closely are
-numerous: music functions previously worked differently when used inside
-or outside of chords.  Now they are the same, including all the
-possibilities of argument parsing.  You can now use music variables
-inside of chords: a construct like
+The following three items are consequences of this change.
+
+@item
+The repetitive chord entry aid @code{q} has been reimplemented.
+Repeated chords are now replaced right before interpreting a music
+expression.  In case the user wants to retain some events of the
+original chord, he can run the repeat chord replacement function
+@code{\chordRepeats} manually.
+
+@item
+String numbers and right hand fingerings on single notes now appear
+without having to be written inside of chord brackets.
+
+@item
+Music functions now work the same when used inside or outside of chords,
+including all the possibilities of argument parsing.  Music variables
+can be used inside of chords: a construct like
 @lilypond[verbatim,quote,ragged-right]
 tonic=fis'
 { <\tonic \transpose c g \tonic> }
 @end lilypond
 @noindent
-would have been unthinkable previously.  You can use
-@code{#@{@dots{}#@}} for constructing chord constituents.  Music
-functions inside of chords are no longer specially treated and thus
-accept the same arguments as outside of chords.  @code{\tweak} now works
-on single notes without needing to wrap them in a chord.  In theory, it
-can also work on command events and lyrics now.  Since that was not
-possible before, it depends on luck on a case-by-case basis whether the
-tweak internals are already receiving the necessary information.  Users
-are asked to report those cases where they find @code{\tweak} not
-working according to reasonable expectations.
+now works as expected.  One can use @code{#@{@dots{}#@}} for
+constructing chord constituents.  @code{\tweak} now works on single
+notes without needing to wrap them in a chord.  Using it on command
+events and lyrics is now possible, but not likely to give results yet.
 
 @item
-As one consequence, it was possible to reimplement the repetitive chord
-entry aid @code{q}.  Repeated chords are now replaced right before
-interpreting a music expression.  In case the user wants to retain
-some events of the original chord, he can run the repeat chord
-replacement function @code{\chordRepeats} manually.
+@code{\tweak} now takes an optional layout object specification.  It can
+be used for tweaking layout objects that are only indirectly caused by
+the tweaked event, like accidentals, stems, and flags:
+
+@lilypond[verbatim,quote,ragged-right,relative=2]
+<\tweak Accidental #'color #red   cis4
+ \tweak Accidental #'color #green es
+                                  g>
+@end lilypond
 
 @item
 Scheme expressions inside of embedded Lilypond (@code{#@{@dots{}#@}})