That's fine. It just took me a couple of minutes to figure out that it was the compile last measures feature making the warning. Maybe a note in the documents saying that the feature can produce oddities.
Knute Snortum (via Gmail) On Sun, Jun 1, 2014 at 11:46 PM, Phil Holmes <[email protected]> wrote: > "Knute Snortum" <[email protected]> wrote in message news:CALmeJxQT5HNp+ > [email protected]... > > The following will emit this spurious warning: Two simultaneous >> tempo-change events, junking this one >> >> %%%%%%%%%%%%%%%%% >> \version "2.18.2" >> >> >> showLastLength = R1 >> >> >> \relative c' { >> >> \tempo 4 = 80 >> >> c4 c c c >> >> \tempo 4 = 90 >> >> c4 c c c >> >> } >> >> -- >> Knute Snortum >> (via Gmail) >> > > In my experience, all of the "skip typesetting" features of LilyPond have > some idiosyncrasies. I'm not convinced it's worth worrying about this. > > -- > Phil Holmes > > > > _______________________________________________ > bug-lilypond mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/bug-lilypond > _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
