Re: RemoveEmptyStaffContext erases previous setting

2010-06-20 Thread Graham Percival
On Sun, Jun 20, 2010 at 03:17:34PM +0100, Phil Holmes wrote: > "Reinhold Kainhofer" wrote in message > news:201002051826.56687.reinh...@kainhofer.com... >> On Friday 05 February 2010 18:05:52 you wrote: >>> On Fri, Feb 5, 2010 at 3:14 PM, Reinhold Kainhofer >>> >>> wrote: >>> > I found out the

Re: RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Graham Percival
On Fri, Feb 05, 2010 at 06:20:23PM +0100, Mats Bengtsson wrote: > If would be pedagogically simpler to realize this difference if the > syntax was separate if you define a context from scratch (as is the > case with \RemoveEmptyStaffContext) or if it's defined by adding onto > an existing context.

Re: RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Reinhold Kainhofer
On Friday 05 February 2010 18:20:23 you wrote: > The simple solution is to change the order, so that you do \layout { > \context { \RemoveEmptyStaffContext } > } > > before any other > > \layout { > \context { \Staff > ... > } > } > That's not easily possible if you want to have globa

Re: RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Reinhold Kainhofer
On Friday 05 February 2010 18:05:52 you wrote: > On Fri, Feb 5, 2010 at 3:14 PM, Reinhold Kainhofer > > wrote: > > I found out the hard way that apparently adding \RemoveEmptyStaffContext > > globally to a score will erase some previous settings. > > Yes. \removeEmptyStaffContext copies the new

Re: RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Mats Bengtsson
Quoting Neil Thornock : My understanding is that LilyPond can only take one \layout block - no? So any subsequent layout block will override the previous one. No! You can have several layout blocks and the accumulated result of all settings is used. I don't think it's buggy at all. You jus

Re: RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Graham Percival
On Fri, Feb 5, 2010 at 3:14 PM, Reinhold Kainhofer wrote: > I found out the hard way that apparently adding \RemoveEmptyStaffContext > globally to a score will erase some previous settings. Yes. \removeEmptyStaffContext copies the new context over the previous one. Or something like this. I re

Re: RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Reinhold Kainhofer
On Friday 05 February 2010 17:50:28 you wrote: > My understanding is that LilyPond can only take one \layout block - > no? So any subsequent layout block will override the previous one. No,that's not true. You can have several layout blocks. Attached is an example, where the first block removes

Re: RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Neil Thornock
My understanding is that LilyPond can only take one \layout block - no? So any subsequent layout block will override the previous one. Have you tested this with settings other than RemoveEmptyStaffContext, to see if two layout blocks will work under any other condition? I don't think it's buggy a

RemoveEmptyStaffContext erases previous setting

2010-02-05 Thread Reinhold Kainhofer
I found out the hard way that apparently adding \RemoveEmptyStaffContext globally to a score will erase some previous settings. In particular, if you have: \layout { \context { \Staff ignoreFiguredBassRest = ##f } } \layout { \context { \RemoveEmptyStaffContext } } then the score wil