> Index: lilypond/Documentation/user/changing-defaults.itely
> diff -u lilypond/Documentation/user/changing-defaults.itely:1.102
> lilypond/Documentation/user/changing-defaults.itely:1.103
> @@ -624,6 +624,21 @@
> It is not possible to collect context changes in a variable, and apply
> them to one @code{\context} definition by referring to that variable.
I happened to see these (unchanged) lines in the patch, which seem
completely wrong to me. The definition of \RemoveEmptyStaffContext
in ly/engraver-init.ly is an excellent counter example, right?
/Mats
>
> +The @code{\RemoveEmptyStaffContext} will override your current
> [EMAIL PROTECTED] variable. If you wish to change the defaults for a
> +staff that uses @code{\RemoveEmptyStaffContext}, you must do so
> +after calling @code{\RemoveemptyStaffContext}, ie
> +
> [EMAIL PROTECTED]
> +\layout @{
> + \context @{
> + \RemoveEmptyStaffContext
> +
> + \override Stem #'thickness = #4.0
> + @}
> [EMAIL PROTECTED]
> [EMAIL PROTECTED] example
> +
>
> @node Defining new contexts
> @subsection Defining new contexts
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
