Hi,
I've bundled a couple of old non-important bugs I found in pre-2.2, which have
not been fixed yet. Plus some new ones.
1. ly/declarations-init.ly starts with "#(ly:set-option 'old-relative)". This
should be removed, right?
2. Top of manual says:
This is the user manual for GNU LilyPond 2.1.x series. (See the bottom of this
page for the exact version number).
s/2.1/2.2/
3. The warnings for old-relative doesn't work well for scores with multiple
files. But anyways I guess the warnings were introduced just as a quick hack
to make input/* work... so it's not really a big issue.
4. Cryptic warning: The following 2 scores are identical, and both do bad
staff changes. But the first example results in a warning that I don't
understand:
"can't change `Staff' to `foo': I'm one myself"
\version "2.2.0"
\score {
\new Staff \notes {
\change Staff=foo
}}
\score {
\new Staff \notes {
\key c\major
\change Staff=foo
}}
\version "2.2.0"
\score {<<
\new Staff \notes { a4 a a a \context Voice=A {a a a a}}
\lyricsto A \new Lyrics \lyrics { a a a a }
>>}
5. Voice change warnings: The following gives 5 warnings but perfect output.
\version "2.2.0"
\score {<<
\new Staff \notes { a4 a a a \context Voice=A {a a a a}}
\lyricsto A \new Lyrics \lyrics { a a a a }
>>}
It would be logical if lyricsto would issue a warning only if lyricsto cannot
find a voice to couple its lyrics to (this would catch all ).
Or, ideally, \lyricsto A could issue one warning iff there is not _exactly
one_ Voice context named A that it can couple the lyrics to.
E.g., this
<<
%\new Staff=up \context Voice=A a
\new Staff=down { a \context Voice=A a }
\lyricsto A \new Lyrics \lyrics { a }
>>
would give a warning iff the first line would be commented out (like "lyricsto
ambiguity: Voice A exists in >1 Staff context" or similar).
Erik
_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
