Re: RemoveEmptyStaffContext erases previous setting

[Phil Holmes]

"Reinhold Kainhofer" <address@hidden> wrote in message 
news:address@hidden
> 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 trying to ensure that reported bugs
> > aren't lost.  If I'm wrong that something looks odd,
>
> I can't see anything obviously wrong, but I might miss something, too. So 
> some
> more details what might be wrong would help enormously...
>
> Cheers,
> Reinhold

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 errors, you cannot be sure any more 
that
the full score or e.g. the  choral score are correct, too!"

So I tried to recreate it and found that 2.12 and 2.13 functioned 
differently, and I attached an image demonstrating that.  But if you say 
it's not a bug and is correct behaviour, I'm happy to forget it.


--
Phil Holmes
Bug Squad