Re: ScholarLy fails with \RemoveEmptyStaffContext

[Graham King]

On Mon, 2015-11-16 at 09:24 +0100, David Kastrup wrote:
> Graham King <address@hidden> writes:
>
> > This took a little while to nail down, but it seems that ScholarLy's
> > annotation engine fails silently when \RemoveEmptyStaffContext is
> > active.  Almost-minimal example attached.
>
> >   \layout {
> > %{ %Toggle this block comment to reveal problem:
> >     \context {
> >       \RemoveEmptyStaffContext
> >     }
> > %}     
>
> What is that supposed to be?  I am not even sure what this does.  Maybe
> we should check that case and flag an error: there is no context
> specified to which this is supposed to apply.  You probably want
> something like a
>
> \Staff
>
> before the \RemoveEmptyStaffContext.
Apologies.  In my enthusiasm to boil this down to a minimal example, I've created an oddball that just looks like Lilypond-abuse. Here it is again with an extraneous staff restored.  
I don't think there is any problem with lilypond itself.  However, either this user or Urs' ScholarLy annotation code has a problem/limitation.

scholarly3.ly
Description: Text document