"Phil Holmes" <m...@philholmes.net> wrote in message
news:km8ll8$of0$1...@ger.gmane.org...
"David Kastrup" <d...@gnu.org> wrote in message
news:87li7sp0bp....@fencepost.gnu.org...
Urs Liska <m...@ursliska.de> writes:
I don't know if it's a regression because I don't know if it
_deliberately_ worked in an earlier version.
But I just checked all versions I still have around and can say that
2.15.40
2.16.0 and
2.17.3
compiled the example correctly
while 2.17.16 crops the bracket as shown in the attachment to my initial
email.
My current /usr/local/lilypond/binary (I only do make install once in a
while) still works and claims to be 2.17.12. Since that version number
is output for everything after 2.17.11, this means that the problem has
been introduced in version 2.17.12 or later.
Someone up for bisection?
Watch this space.
git bisect bad
7b2cb93fc69c7d7c45f0ae6495f688752efeb107 is the first bad commit
commit 7b2cb93fc69c7d7c45f0ae6495f688752efeb107
Author: Mike Solomon <m...@apollinemike.com>
Date: Sat Mar 23 19:09:28 2013 +0100
Fixes manual beaming over rests and vertical spacing problem (issue
3242)
--
Phil Holmes
Bug Squad
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
