Am Montag, 21. Juni 2010, um 16:09:57 schrieb Phil Holmes:
> Well, it started by you saying:
>
> "Is this a bug? In my eyes, it is quite severe, because it means you can't
> trust lilypond any more. If you check e.g. the individual parts (which do
> not
> add the RemoveEmptyStaffContext) for erro
"Reinhold Kainhofer" wrote in message
news:201006202256.43475.reinh...@kainhofer.com...
Am Sonntag, 20. Juni 2010, um 22:53:06 schrieb Phil Holmes:
Well - the "oddity" that I identified was that a bug had been reported,
and
that 2.12 behaved differently from 2.13.
In what respect did it beha
Am Sonntag, 20. Juni 2010, um 22:53:06 schrieb Phil Holmes:
> Well - the "oddity" that I identified was that a bug had been reported, and
> that 2.12 behaved differently from 2.13.
In what respect did it behave differently?
> I'm not wise enough to know
> whether this is wrong or not, but am tryi
"Reinhold Kainhofer" wrote in message
news:201006202000.56332.reinh...@kainhofer.com...
Am Sonntag, 20. Juni 2010, um 16:17:34 schrieb Phil Holmes:
"Reinhold Kainhofer" wrote in message
> I think RESC should be somehow recoded to apply only the relevant
> changes
> when it is actually called
2010/6/20 Reinhold Kainhofer :
> Having said that, RemoveEmptyStaffContext has also been fixed in the 2.13
> branch: You should now use
> \context {\Staff
> \RemoveEmptyStaves
> }
> rather than
> \context {
> \RemoveEmptyStaffContext
> }
>
> The former no longer erases previous settings, while t
Am Sonntag, 20. Juni 2010, um 16:17:34 schrieb Phil Holmes:
> "Reinhold Kainhofer" wrote in message
> > I think RESC should be somehow recoded to apply only the relevant changes
> > when it is actually called, but not store the whole Staff context at
> > definition time.
>
> I've had a long look
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
"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 hard way that apparently adding
> \RemoveEmptyStaffContext
> globally to a score
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
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
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
11 matches
Mail list logo
