Trevor Daniels wrote Wednesday, January 19, 2011 12:43 PM
Keith OHara wrote Wednesday, January 19, 2011 7:25 AM
Follow-up patch attached.
This looks fine to me. I'll push it in a day or two if there are
no adverse comments.
Pushed.
Trevor
___
Keith OHara wrote Wednesday, January 19, 2011 7:25 AM
Follow-up patch attached.
The misleading bit was the implication that the properties always
contain alists, when one of them is by default a function
returning whichever alist is appropriate depending on whether the
staff is in a group
On Sun, 16 Jan 2011 01:51:19 -0800, Trevor Daniels
wrote:
I've pushed this patch, but isn't the immediately preceding text
misleading,
in that it says,
"The following example demonstrates the two ways these alists can be
modified. The first declaration updates one key-value individually,
and
es the property:"?
But the first method fails on (at least) staff-staff-spacing.
Trevor
- Original Message -
From: "Keith OHara"
To: "James Worlton" ;
Cc: ; "Trevor Daniels"
Sent: Sunday, January 16, 2011 1:09 AM
Subject: Re: global staff-staff sp
On Sun, Jan 16, 2011 at 09:46:42AM +, Graham Percival wrote:
> I know that you were working on an old file which doesn't follow
> this policy, but would you mind making the examples follow this?
Never mind; it's fine as it is.
Cheers,
- Graham
___
On Sat, Jan 15, 2011 at 05:09:51PM -0800, Keith OHara wrote:
> Dear docs editors,
> Patch attached.
> (I had to wrap long lines of .ly; tried to pick a consistent indentation.)
Doc policy is 2-space indents, and in the case where you're
wrapping a long line, indent the first "wrapped" line by 2 s
James Worlton gmail.com> writes:
The following code compiles, but the spacing override in the layout block fails. The
layout block code was copied and pasted into my test directly from the NR 4.4.1
"Within-system spacing properties". ...
\override VerticalAxisGroup #'staff-staff-spacing #'b
