bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RemoveEmptyStaffContext erases previous setting


From: Phil Holmes
Subject: Re: RemoveEmptyStaffContext erases previous setting
Date: Sun, 20 Jun 2010 21:53:06 +0100

"Reinhold Kainhofer" <address@hidden> wrote in message news:address@hidden
Am Sonntag, 20. Juni 2010, um 16:17:34 schrieb Phil Holmes:
"Reinhold Kainhofer" <address@hidden> 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 at this and can confirm that there are some slightly
odd things going on, and variations between 2.12 and 2.13. Please see the
attached image and let me have your thoughts.

Ahm, can you please tell me what odd things you are observing in these
examples?

The horizontal spacing is exactly the same, the only difference has nothing to do with RemoveEmptyStaffContext, but rather with figured bass figures on rests
(which in some cases were suppressed in 2.12, but that has been fixed
meanwhile, so that figures always correctly appear when you write them in your
lilypond code).

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 the latter still does in 2.13 (we kept this behaviour for reasons of backwards compatibility to prevent
"regressions" in existing scores...

Cheers,
Reinhold

Well - the "oddity" that I identified was that a bug had been reported, and that 2.12 behaved differently from 2.13. I'm not wise enough to know whether this is wrong or not, but am trying to ensure that reported bugs aren't lost. If I'm wrong that something looks odd, I'm happy and won't raise it as a bug report.

--
Phil Holmes
Bug Squad





reply via email to

[Prev in Thread] Current Thread [Next in Thread]