Originally created by: *anonymous
Originally created by: colingh...@gmail.com
Originally owned by: benko....@gmail.com
Ben Rudiak-Gould reported here:
http://lists.gnu.org/archive/html/bug-lilypond/2012-12/msg00064.html
as follows:
% The end of the ligature bracket is not printed
\version "2.17.8"
{ \[ c'1 \break d'1 \] }
Originally posted by: mts...@gmail.com
Sets bracket-visibility to true for ligature brackets
http://codereview.appspot.com/6946077
Labels: Patch-new
Originally posted by: mts...@gmail.com
Sets bracket-visibility to true for ligature brackets
http://codereview.appspot.com/6946077
Originally posted by: dak@gnu.org
Patchy the autobot says: passes tests. The regtest input/regression/ambitus-with-ligature.ly now shows both a ligature as well as a ligature bracket. Is this effect intentional?
Labels: -Patch-new Patch-review
Originally posted by: ColinPKC...@gmail.com
(No comment was entered for this change.)
Labels: -Patch-review Patch-countdown
Owner: mts...@gmail.com
Originally posted by: benko....@gmail.com
David: the effect is probably not intended, but implicitly required by _not_ \remove'ing "Ligature_bracket_engraver". I understand less and less why brackets were seen at all so long.
Originally posted by: ColinPKC...@gmail.com
Counted down to 20121223, please push.
Labels: -Patch-countdown Patch-push
Originally posted by: benko....@gmail.com
ping
Originally posted by: mts...@gmail.com
Pushed as [r2502db9d63fd5c0ac2171e3c70943510d4456746].
Labels: Fixed_2_17_9
Status: Fixed
Originally posted by: mts...@gmail.com
(No comment was entered for this change.)
Labels: -Fixed_2_17_9 Fixed_2_17_10
Originally posted by: benko....@gmail.com
make a regtest more reasonable
follows up [r2502db9d63fd5c0ac2171e3c70943510d4456746] for issue 3037
http://codereview.appspot.com/7103052
Labels: -Patch-push Patch-new
Owner: benko....@gmail.com
Status: Started
Originally posted by: pkx1...@gmail.com
Pass Make, Make check and a full make doc.
Reg test attached
Labels: -Fixed_2_17_10 -Patch-new Patch-review
Originally posted by: pkx1...@gmail.com
(No comment was entered for this change.)
Originally posted by: ColinPKC...@gmail.com
(No comment was entered for this change.)
Labels: -Patch-review Patch-countdown
Originally posted by: dak@gnu.org
This should better have been an issue of its own rather than coattailing on an already fixed issue since regtest and main issue have been committed to different versions. That makes handling the issues properly rather hard to do.
At any rate, please push.
Labels: -Patch-countdown Patch-push
Originally posted by: benko....@gmail.com
agreed, sorry.
pushed to staging as
[r2502db9d63fd5c0ac2171e3c70943510d4456746]
Originally posted by: dak@gnu.org
No, the followup patch is not [r2502db9d63fd5c0ac2171e3c70943510d4456746]. That was the original one from Mike.
This, in contrast, was
commit [r89cb4a2432c55f2b28ef4b7c976e4d47b6bb4195]
Author: Benkő Pál <benko.pal@gmail.com>
Date: Thu Jan 10 23:00:25 2013 +0100
issue 3037: follow up [r2502db9d63fd5c0ac2171e3c70943510d4456746]
It would appear to have been included in 2.17.11. Please try not to make life of the Bug Squad harder by providing false information and omitting to update the status of an issue.
And something might be said for more descriptive commit messages as well.
Labels: -Patch-push Fixed_2_17_11
Originally posted by: mts...@gmail.com
(No comment was entered for this change.)
Status: Fixed
Originally posted by: Elu...@gmail.com
(No comment was entered for this change.)
Status: Verified