On Fri, Feb 25, 2011 at 4:02 PM, Phil Holmes <[email protected]> wrote:
> "Keith OHara" <[email protected]> wrote in message > news:[email protected]... > > Phil Holmes <mail <at> philholmes.net> writes: >> >> With the code at the end of this report, I get pretty good output, but >>> get >>> the following in the log file: >>> >>> warning: too many colliding rests >>> >>> >> The warning is not always a false alarm, sometimes LilyPond fails to place >> the >> two rests "correctly". I suspect that her rules for placement require >> keeping >> rests away from the line of the third voice, so the warning tells us she >> cannot >> not satisfy all her rules. >> >> \version "2.12" >> \new Staff << >> \new Voice { \voiceOne s4 } % just a skip >> \new Voice { \voiceTwo d'8 r } >> % warning before failure if voiceFour, not so bad if voiceThree. >> \new Voice { \voiceFour a'8 r } >> %{%} >> >> >> I suppose desired behavior could be for LilyPond to prioritize collisions >> over >> staying out of the line of the third voice, or something like that, but >> that >> seems more an enhancement request than bug report. >> > > My preference is for all my lily source to compile cleanly, so a warning > when there's actually no problem is annoying. Given the other collisions > that can occur and don't produce a warning, I'd view this warning when > there's no collision as a bug. Low priority, but still a bug. > > -- > Phil Holmes > Bug Squad > > Greetings, Phil and Keith - This has been submitted as issue 1547 : http://code.google.com/p/lilypond/issues/detail?id=1547 Ralph _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
