On Sat, May 16, 2015 at 07:36:30AM +0100, James Lowe wrote:
> On 15/05/15 22:38, H. S. Teoh wrote:
[...]
> > % - Note: this is not the same as issue 913; padding the first voice
> > % to have the same length as the second does not change the wrong
> > % tuple bracket.
% The triplet in the first argument to \partcombine is wrongly
% formatted in the output; the tuplet bracket only spans the two quarter
% rests, whereas it should span both rests and the single note.
%
% - Note: this is not the same as issue 913; padding the first voice
% to have the same length
% \partcombine should have produced a combined staff containing d'1 in
% the first bar, f'1 in the second and 3rd bars, and 1 chords in
% the next 2 bars. However, it seems to interact badly with \tag, and
% the output has a missing f1' in the second bar, a stray rest in the
% 3rd bar, and a missin
# This bug appears to be similar or identical to issue 601: accidentals
# cause cross-staff arpeggios to collide.
#
# The following example shows the note a4 being struck through by the arpeggio
# lines in both lilypond-2.18.2 and git HEAD (lilypond-2.19.16). The
# attached image shows the output f
