This is a Gentoo box with Lilypond built from source. Since this bug
did not exist in late versions of Lilypond 2.7.x, this is a
regression. I have not yet gone backwards through the 2.7 branch to
see when the bug was introduced, but I am planning on doing so this week.
Hmm. On further investigation this bug goes quite a ways back in the 2.7
tree, with the introduction of the use of VerticalAxisGroup to set
Y-extents for staves. As I recall, Lilypond development went into
"brain surgery" mode about this time, so deconstructing exactly what
introduced this bug could be very hairy.
I hope this can be resolved soon, because otherwise I'm going to have to
revert to 2.6.5 (or 2.7.12 for shape-note pieces).
--Daniel
P.S. For the sake of completeness, here is my system layout:
Gentoo Linux
Guile 1.8.0
AFPL Ghostscript 8.53 (with the global glyph names patch applied)
Python 2.4.2
Pango 1.12.1
Freetype 2.1.9
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
