From: Mark Polesky <markpolesky@yahoo.com>
Date: Wed, 8 Dec 2010 10:39:14 +0000 (-0800)
Subject: Doc: NR 5.3.6: Update alist example; minor edits.
X-Git-Tag: release/2.13.42-1~1
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=a5285f0b4e7391da01f8d65e64ca710bae4cac62;p=lilypond.git

Doc: NR 5.3.6: Update alist example; minor edits.
---

diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely
index 69d6fe3741..b05bc22c4c 100644
--- a/Documentation/notation/changing-defaults.itely
+++ b/Documentation/notation/changing-defaults.itely
@@ -2000,13 +2000,15 @@ For example, to reduce the space between adjacent staves in a
 staff-group, use the @code{staff-staff-spacing} property of the
 @code{StaffGrouper} grob.  The property is an alist with four
 keys: @code{basic-distance}, @code{minimum-distance},
-@code{padding}, and @code{stretchability}.  Three of the four keys
-have initialized default values; these are listed in the
-@qq{Backend} section of the Internals Reference (see
-@rinternals{StaffGrouper}):
+@code{padding}, and @code{stretchability}.  The standard settings
+for this property are listed in the @qq{Backend} section of the
+Internals Reference (see @rinternals{StaffGrouper}):
 
 @example
-'((basic-distance . 9) (minimum-distance . 7) (padding . 1))
+'((basic-distance . 9)
+  (minimum-distance . 7)
+  (padding . 1)
+  (stretchability . 5))
 @end example
 
 One way to bring the staves closer together is by reducing the
@@ -2073,16 +2075,15 @@ declarations are equivalent:
 @end example
 
 One (possibly unintended) consequence of this is the removal of
-any @emph{initialized} default values that are set in an
-initialization file and loaded each time an input file is
-compiled.  In the above example, the initialized default values
-for @code{padding} and @code{minimum-distance} (defined in
-@file{scm/define-grobs.scm}) are reset to their default-when-unset
-values (zero for both keys).  Defining a property or variable as
-an alist (of any size) will always reset all unset key-values to
-their default-when-unset values.  Unless this is the intended
-result, it is safer to update key-values individually with a
-nested declaration.
+any standard settings that are set in an initialization file and
+loaded each time an input file is compiled.  In the above example,
+the standard settings for @code{padding} and
+@code{minimum-distance} (defined in @file{scm/define-grobs.scm})
+are reset to their default-when-unset values (zero for both keys).
+Defining a property or variable as an alist (of any size) will
+always reset all unset key-values to their default-when-unset
+values.  Unless this is the intended result, it is safer to update
+key-values individually with a nested declaration.
 
 @warning{Nested declarations will not work for context property
 alists (such as @code{beamExceptions}, @code{keySignature},