Re: [bug?] \lyricsto with lyrics above notes

[Juergen Reuter]

Hi, Mats!

Fully agreed, especially your last point.  One point though: You ask why 
it should?  Well, what for example happens exactly with the "{ s1 }"?  
Currently, it seems like the "s1" is thrown away, as anything else that is 
put between these two braces.  What if future versions somehow merge the 
two lyrics definitions?  That may result in unexpected side effects 
(additional vertical space, bar check warnings, whatever, ...).  Maybe, 
replacing "{ s1 }" by "{ }" is a little bit safer (provided that future 
versions will still allow empty blocks)?  Ok, I am quite nitpicking here, 
but I am just feeling uncomfortable with the current "solution".

Greetings,
Jürgen

On Fri, 3 Sep 2004, Mats Bengtsson wrote:

> 
> 
> Juergen Reuter wrote:
> > Ok, it finally seems to work over here; changing "hi4" to "hi8" has no 
> > effect (as expected).  Still, I fear that the "{ s1 }" trick of the 
> > example in section 3.3.1 of the manual is likely to break sooner or later 
> > in future versions of lily.
> 
> Why should it? The principles behind this trick are:
> - The name of a context determines it uniquely, i.e. if you say
>    \context Lyrics = mylyrics at two different places in a .ly file,
>    both pieces of lyrics will be part of the same lyrics context and
>    therefore placed on the same vertical position.
> - What I said above is true under the condition that the context
>    is "kept alive", i.e. that the first \context Lyrics = myname contains
>    something at least up til the point in the piece where the
>    second one appears.
> 
> 
> Still, I find it a bit strange that it should be so hard to let
> \lyricsto refer to a Voice context that appears later in the .ly file,
> which is the reason we have to play all these tricks.
> 
>    /Mats
> 
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>