Carl Sorensen <c_soren...@byu.edu> writes: > On 7/27/11 9:53 AM, "David Kastrup" <d...@gnu.org> wrote: > >> "Phil Holmes" <m...@philholmes.net> writes: >> >>> incompatible-stem-warning.log: lots of changed lines: a sample: >>> -/main/src/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-rel >>> ease-unstable/input/regression/incompatible-stem-warning.ly:16:20: >>> warning: adding note head to incompatible stem (type = 1/2) >>> +/main/src/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-rel >>> ease-unstable/input/regression/incompatible-stem-warning.ly:16:20: >>> warning: adding note head to incompatible stem (type = 1/4) >>> << c'2 >>> e'1 >> >> >> Those are mine (it was the less invasive of two accidental commits, so I >> dit not revert it): the code unifies the stem types before deciding >> whether to complain, so there should be fewer warnings all in all. >> >> However, this results in a warning being called out for a type 1/4 stem >> when there has been no 1/4 note (the 1/4 stem is the same as an 1/2 >> stem). >> >> If people find that too confusing, I can offer to save the original >> duration and use that for wording the complaint. > > I would prefer that alternative, unless the overhead is significant. This > error message is more confusing than it should be.
Will do. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
