Phil Holmes-2 wrote:
This looks to me like correct behaviour. You've created extra Lyrics
contexts, and Lilypond stacks them one above the other. This is as
illustrated in the NR. If I was doing what you're showing, I would use …
hi Phil
sorry to insist on this topic - but since i could not find any
documentation
about my approach i would like to make sure it will last longer (at least
it
was also working with 2.12.3).
there are many advantages with this - beneath the solution for the dying
Lyrics contexts (see Francisco' problem) i'd like to specially mention the
possibility to define properties in temporary contexts (voices, lyrics,
dynamics…) which would remain active also when a context has been closed
and
reopens.
there is also the inconvenience that such contexts must be defined by the
user before he can actually start to use it, and the context must be
named -
maybe a solution to this could be found.
is there a reason why this approach is not supported or propagated!?
thanks
Eluze
ps: i'm not so much interested in discussing if it is a bug or not - it is
just a difficult situation to handle with the "normal" usage of temporary
contexts.
pps: on the french Lilypond list there was another real case that could be
solved with this approach.