Updates:
Status: Verified
Comment #37 on issue 11 by ma...@gregoriana.sk: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
(No comment was entered for this change.)
___
bug-lilypond mailing li
Updates:
Status: Fixed
Labels: fixed_2_15_20
Comment #36 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Pushed to staging. Commit 6e0254ea58791469412846c3039b6029199200e3
Verify with inpu
Comment #35 on issue 11 by k-ohara5...@oco.net: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Carl, my fix to issue 1723 changes the code for beams above rests.
I thought that bug might explain the difficulties you had earlier, but
after loo
Updates:
Labels: -Patch-countdown Patch-push
Comment #34 on issue 11 by colinpkc...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Counted down to 2013
___
bug-lilypond mailin
Comment #32 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
They are all correct.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://list
Updates:
Labels: -Patch-countdown Patch-review
Comment #31 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Carl,
I reran the patch again on a new build but still only got that one reg test
show up.
Comment #29 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
OK, so you got the new regtests
# input/regression/beamlet-point-toward-beat.ly
# input/regression/beamlet-test.ly
Why they didn't
Comment #28 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Carl,
I went back and reapplied the patch:
--snip--
lowe@jlowe-lilybuntu2:~/lilypond-git$ git status
# On branch master
# Changed but not updated:
Comment #27 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
This regtest difference is intentional.
There should also be two new regtests, I believe. Are they not included?
Thanks for all you do, James!
Updates:
Labels: -Patch-new Patch-review
Comment #26 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Passes Make and one reg test diff attached,
james
Attachments:
Screenshot.png 72.7 KB
___
Updates:
Labels: -Patch-needs_work Patch-new
Comment #25 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
New patch set.
___
bug-lilypond mailing list
bug
Updates:
Labels: -Patch-new Patch-needs_work
Comment #24 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Make passes but make check fails on
\sourcefilename
"/home/jlowe/lilypond-git/input/regression/b
Comment #23 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Sorry, I left out the Rietveld code link
http://codereview.appspot.com/4941041/
___
bug-lilypond ma
Updates:
Labels: -Patch-needs_work Patch-new
Comment #22 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
New patch set uploaded
Carl
___
bug-lilypond m
Updates:
Labels: -Patch-review Patch-needs_work
Comment #21 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Don't know how I missed that change. Patch needs more work.
Thanks,
Carl
Updates:
Labels: -Patch-new Patch-review
Comment #20 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Passes Make and reg test diff is attached.
Attachments:
Screenshot.png 49.6 KB
___
Updates:
Labels: -Patch-needs_work Patch-new
Comment #19 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
New patch up that appears to work.
___
bug-lilyp
Updates:
Labels: -Patch-review Patch-needs_work
Comment #18 on issue 11 by colinpkc...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Has there been a new patchset since Aug 30? AFAICS, this is still being
worked over.
_
Updates:
Labels: -Priority-Low -Patch-needs_work Patch-review
Comment #17 on issue 11 by percival.music.ca: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
(No comment was entered for this change.)
_
Updates:
Labels: -Patch-review Patch-needs_work
Comment #16 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Hmm -- it didn't work this way for me. Apparently there's still something
wrong.
I'll
Comment #15 on issue 11 by k-ohara5...@oco.net: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
The change to beam-funky.ly is not desired.
Carl made one revision already to address subdivided beams, but
beam-funky.ly still comes out wrongly.
Updates:
Labels: -Patch-new Patch-review
Comment #14 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
passes make, one reg test change - probably expected. Attached.
Attachments:
Screenshot.png
Updates:
Labels: -Patch-needs_work Patch-new
Comment #13 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Patch works on subdivision now.
Thanks,
Carl
Updates:
Labels: -Patch-new Patch-needs_work
Comment #12 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
As is, the patch breaks subdivision.
___
bug-lil
Updates:
Status: Started
Owner: carl.d.s...@gmail.com
Labels: Patch-new
Comment #11 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Patch up for review.
http://codereview.appspot.com
Updates:
Owner: ---
Comment #10 on issue 11 by percival.music.ca: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of
Comment #9 on issue 11 by percival.music.ca: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Hmm, can we get this image displayed inline?
Attachments:
foo.preview.png 2.6 KB
--
You received this message because you are listed in the
Updates:
Owner: percival.music.ca
Comment #8 on issue 11 by jameseli...@googlemail.com: beamlet on wrong side
of tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
(No comment was entered for this change.)
--
You received this message because you are listed in the
Updates:
Owner: ---
Comment #7 on issue 11 by jameseli...@googlemail.com: beamlet on wrong side
of tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC f
Issue 11: beamlet on wrong side of tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Comment #6 by hanwenn:
Re defect vs. enhancement. - I use this field to prioritize fixes. Generally
defects (we promised it would work) get attention more quickly, but
require less work
t
Issue 11: beamlet on wrong side of tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Comment #5 by v.villenave:
(Reproduced with 2.11.47.) I agree with Comment 2 btw.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because yo
Issue 11: beamlet on wrong side of tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Comment #4 by gpermus:
Type-enhancement means that it requires new code to implement.
I appreciate the effort in finding a real-world example, but this does
not help us
fix the bug -- for t
Issue 11: beamlet on wrong side of tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Comment #3 by mvdborre:
http://mutopiaproject.org/ftp/KnjzeF/knjze12monferE/knjze12monferE-a4.pdf
This a real world example of the problem.
--
You received this message because you are li
Issue 11: beamlet on wrong side of tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Comment #2 by paconet.org:
IMO this is a bit ugly and should be a Type-Defect but I don't know
really what are
the labeling criteria
--
You received this message because you are listed i
34 matches
Mail list logo
