On Thu, Nov 5, 2009 at 9:24 AM, David Kastrup <d...@gnu.org> wrote: > That being said: if someone wants to investigate further and a > workaround can be found that causes the same result on correct systems > and does not trigger the problem on evince, that would be worth > including.
It has been made clear in the past that evince is not our friend: http://lists.gnu.org/archive/html/lilypond-devel/2007-11/msg00135.html http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00852.html > It has been my experience as a package maintainer that after the > hundredth time of putting the blame where it belongs, it gets tiresome. > Versions with this bug, even if it gets fixed immediately, will be > around for years, and dealing with the reports is a resource drain. Ditto, that's already been discussed -- and dismissed by Han-Wen: http://lists.gnu.org/archive/html/lilypond-devel/2007-07/msg00075.html http://lists.gnu.org/archive/html/lilypond-user/2007-07/msg00506.html (Which led our late developer Rune to tell me once: "The first rule of LilyPond is: Han-Wen always wins :-)" ) Cheers, Valentin _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
