Re: The built-in template satb.ly fails in 2.19.16

[Trevor Daniels]

David Kastrup wrote Saturday, March 14, 2015 1:25 PM
Subject: Re: The built-in template satb.ly fails in 2.19.16


> "Trevor Daniels" <address@hidden> writes:
>
>> That seems to be it, sort of.  Below I've simulated the
>> rather bizarre structure the satb.ly template generates.
>> This causes the last three notes of the Soprano line and
>> all the lyrics to vanish, although no error is generated.
> 
> Well, the solution to issue 2010 kills off associated lyrics contexts
> when they become (rather than already are) the only thing left in a
> <<...>> construct.  But in this case, the controlling context is
> actually outside.  The problem of 2010 was that if the controlling
> context in a <<...>> construct dies, the associated lyrics have to quit
> at the same timestep rather than wait for another timestep, or the
> <<...>> construct will throw the whole timing of LilyPond off.

Yes, 2010 may still be involved, but the problem arises 
in this particular case when the Descant music is empty, 
and there is nothing else to keep the context alive.
 
> I'm not sure there is a sane way within the current design (which uses
> the run_always flag for associated lyrics) to make this work in
> arbitrary complex <<...>> constructs.

It's a bit hackish, but maybe determine the longest music
in the ChoirStaff and ensure all the contexts are that
long by adding spacer rests in parallel to that length.
 
> Maybe there is a better solution for issue 2010 but I've spent a _lot_
> of time playing around with that one.

Please don't spend longer on 2010.  At least not until
I've explored all options for fixing satb.ly.  There are
far more important things for you to do.

Trevor