I don't see anything that's non-synchronized here and I don't really
agree on the
title of the bug report. What the example shows is simply a use of
simultaneous
and sequential combinations of contexts.
{<< ... ... >> << ... ... >> }
which is well-defined and nothing strange. The syntax is clearly relevant.
It seems that it's the \lyricsto that causes the problem, but again I
don't see any
reason why it shouldn't work as expected.
/Mats
Valentin Villenave wrote:
2008/10/28 Mats Bengtsson <[EMAIL PROTECTED]>:
This is weird and looks like a bug to me, so I forward it to bug-lilypond.
Added as http://code.google.com/p/lilypond/issues/detail?id=702
LilyPond is not good at printing non-synchronized contexts, we've
already noticed that.
Cheers,
Valentin
--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
