2008/10/29 Mats Bengtsson <[EMAIL PROTECTED]>:
> 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.
Yes, this is what I mean by non-synchr
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 clear
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
_
This is weird and looks like a bug to me, so I forward it to bug-lilypond.
However, you may want to reorganize your score along the lines of
the email "Re: Adding a staff in the middle of a piece" I sent on
lilypond-user some minutes ago, which shows how to switch a stave back
and forth between