This is a bug in the documentation. What happens is that
the command \new puts more emphasis on the meaning of
the word "new" than the fact that you have specified an
explicit name of the context. So, the second \new Staff = down
will not result in the already defined Staff context with the name
"down". However, if you say
\context Staff = down {
\new Voice {g a b c \change Staff = up d e fis g }
}
it should work. See "Creating contexts" in the manual
for more details.
/Mats
Sandy Scott wrote:
Not quite sure what the ettiquite for posting a bug that is quite probably my
incompetence, but I'll just straight to it:
This is the code from the Manual Staff Switches Page, with a few very small
changes (added the version comment and also put some notes in the voice) to
make it produce some output:
*******************************************
\version "2.10.0"
<<
\new Staff = "up" {
\skip 1 * 10 % keep staff alive
}
\new Staff = "down" {
\skip 1 * 10 % idem
}
(insert two "greater-than" signs here*)
\new Staff = down
\new Voice {g a b c \change Staff = up d e fis g }
*******************************************
However, contrary to my expectations, this produces 3 staves, not 2 - the top
two are blank and the third contains the notes, but obviously without any staff
changes.
Is this a bug, a problem with the Docs, or just me being stupid?
Sandy Scott
*PS. Is there a tidier way of getting round the top-posting filter?
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
