Issue 1944 in lilypond: Patch: lily/bezier.cc: Avoid a floating point compare

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1944 by k-ohara5...@oco.net: Patch: lily/bezier.cc: Avoid a floating point compare http://code.google.com/p/lilypond/issues/detail?id=1944 lily/bezier.cc: Avoid a floating point compare http://codereview.appspot.com/5121042

Re: Issue 1931 in lilypond: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised

Updates: Labels: -Priority-Low Comment #4 on issue 1931 by percival.music.ca: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised http://code.google.com/p/lilypond/issues/detail?id=1931 no, we're not using priorities.

Re: Issue 1852 in lilypond: manuals needs more explicit dependencies

Comment #26 on issue 1852 by percival.music.ca: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 Just follow the instructions in comment 0 of issue 1491. Except you want to fix the handling of .texi files instead of .scm files. ___

Re: Issue 1910 in lilypond: Implement define-event-function

Updates: Status: Verified Comment #5 on issue 1910 by colinpkc...@gmail.com: Implement define-event-function http://code.google.com/p/lilypond/issues/detail?id=1910 (No comment was entered for this change.) ___ bug-lilypond mailing list bu

Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions

Updates: Status: Verified Comment #17 on issue 935 by colinpkc...@gmail.com: Enhancement: optional arguments in music functions http://code.google.com/p/lilypond/issues/detail?id=935 (No comment was entered for this change.) ___ bug-lilypo

Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

Status: Accepted Owner: Labels: Type-Critical Regression OpSys-OSX New issue 1943 by colinpkc...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 Previous Issue 1919:lilypond 2.15.12 fails on darwin-ppc seems to be resolved fo

Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc

On 11-09-27 07:17 AM, lilyp...@googlecode.com wrote: Comment #12 on issue 1919 by stans...@gmail.com: lilypond 2.15.12 fails on darwin-ppc http://code.google.com/p/lilypond/issues/detail?id=1919 Since the issue with the ppc version has been corrected, a new report regarding the x86 version s

Re: Issue 1938 in lilypond: MIDI volume can exceed maximum value (Rietveld 5134047)

Updates: Labels: -Patch-new Patch-review Comment #2 on issue 1938 by pkx1...@gmail.com: MIDI volume can exceed maximum value (Rietveld 5134047) http://code.google.com/p/lilypond/issues/detail?id=1938 Passes make and reg tests ___ bug-lilyp

Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account

Updates: Labels: -Patch-new Patch-needs_work Comment #19 on issue 155 by pkx1...@gmail.com: \parenthesize does not take accidentals into account http://code.google.com/p/lilypond/issues/detail?id=155 Passes make but I get some reg test 'crossing fingers' messages --snip-- /home/jlo

Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py

Updates: Owner: mts...@gmail.com Labels: -Patch-new Patch-push Comment #3 on issue 1941 by pkx1...@gmail.com: Patch: Fixes to projecthosting_upload.py http://code.google.com/p/lilypond/issues/detail?id=1941 Guessing I don't need to test this from Graham's last comment. _

Re: Issue 1927 in lilypond: 2.15.2 doesn't build anymore on Mageia

Updates: Status: Accepted Labels: Type-Build Needs-evidence Comment #1 on issue 1927 by brownian.box: 2.15.2 doesn't build anymore on Mageia http://code.google.com/p/lilypond/issues/detail?id=1927 (No comment was entered for this change.)

Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc

Comment #12 on issue 1919 by stans...@gmail.com: lilypond 2.15.12 fails on darwin-ppc http://code.google.com/p/lilypond/issues/detail?id=1919 Since the issue with the ppc version has been corrected, a new report regarding the x86 version should be opened. 2.15.13 does not run on x86. As p

Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc

Comment #11 on issue 1919 by stans...@gmail.com: lilypond 2.15.12 fails on darwin-ppc http://code.google.com/p/lilypond/issues/detail?id=1919 Since the issue with the ppc version has been corrected, a new report regarding the x86 version should be opened. 2.15.13 does not run on x86. As p

Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc

Comment #10 on issue 1919 by fiee.vis...@gmail.com: lilypond 2.15.12 fails on darwin-ppc http://code.google.com/p/lilypond/issues/detail?id=1919 OSX 10.4.11 PPC. 2.14.2 is running, 2.15.13 runs also. ___ bug-lilypond mailing list bug-lilypond@gn

Re: Issue 1931 in lilypond: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised

Comment #3 on issue 1931 by pkx1...@gmail.com: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised http://code.google.com/p/lilypond/issues/detail?id=1931 Seemed so from the last few weeks. If I am wrong about this sorry.

Re: Issue 1812 in lilypond: NR Context Layout Order rewrite (5.1.7)

Updates: Labels: -Patch-countdown Patch-needs_work Comment #9 on issue 1812 by pkx1...@gmail.com: NR Context Layout Order rewrite (5.1.7) http://code.google.com/p/lilypond/issues/detail?id=1812 Graham commented ___ bug-lilypond mailing lis

Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc

Comment #9 on issue 1919 by fiee.vis...@gmail.com: lilypond 2.15.12 fails on darwin-ppc http://code.google.com/p/lilypond/issues/detail?id=1919 OSX 10.5.8 Intel. 2.15.8 is running, 2.15.13 crashes immediately: Process: LilyPond [3010] Path:/.../LilyPond.app/Contents/MacOS

Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py

Comment #2 on issue 1941 by mts...@gmail.com: Patch: Fixes to projecthosting_upload.py http://code.google.com/p/lilypond/issues/detail?id=1941#c2 Fixes to projecthosting_upload.py http://codereview.appspot.com/5144045 ___ bug-lilypond mailing lis

Re: Issue 1942 in lilypond: Patch: Fixes to projecthosting_upload.py

Updates: Status: Duplicate Comment #1 on issue 1942 by mts...@gmail.com: Patch: Fixes to projecthosting_upload.py http://code.google.com/p/lilypond/issues/detail?id=1942 ugh...sorry, duplicate issue (working on git-cl) ___ bug-lilypond mai

Issue 1942 in lilypond: Patch: Fixes to projecthosting_upload.py

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1942 by mts...@gmail.com: Patch: Fixes to projecthosting_upload.py http://code.google.com/p/lilypond/issues/detail?id=1942 Fixes to projecthosting_upload.py http://codereview.appspot.com/5144045 _

Re: Issue 1852 in lilypond: manuals needs more explicit dependencies

Comment #25 on issue 1852 by janek.li...@gmail.com: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 Indeed i should've done this myself, sorry! I've remembered that one of the new contributors uploaded his patch himself and i was mistakenly

Re: Issue 1491 in lilypond: git-cl hangs when uploading patches due to bad mime-type

Updates: Labels: -Type-Maintainability Type-Critical Comment #5 on issue 1491 by percival.music.ca: git-cl hangs when uploading patches due to bad mime-type http://code.google.com/p/lilypond/issues/detail?id=1491 this has reached the point of impeding serious contributors, so it's C

Re: Issue 1852 in lilypond: manuals needs more explicit dependencies

Comment #24 on issue 1852 by percival.music.ca: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 I quite agree; sorry, I should have prefixed my comment 22 with a "Janek:". It's his responsibility to get your patch visible. ___

Re: Issue 1852 in lilypond: manuals needs more explicit dependencies

Comment #23 on issue 1852 by julien.r...@gmail.com: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 I did use Graham's git-cl since the "official" one went offline. I think the patch did not get published to lilypond-de...@gnu.org because I

Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:'

Comment #5 on issue 1008 by percival.music.ca: Some warning/error messages are not prefixed with 'warning:'/'error:' http://code.google.com/p/lilypond/issues/detail?id=1008 I think that all the "_i" are "info" messages, which are good. ___ bug-lil

Re: Issue 1852 in lilypond: manuals needs more explicit dependencies

Updates: Status: Accepted Comment #22 on issue 1852 by percival.music.ca: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 Get the patch uploaded correctly before you worry about the cc. Make sure the mime type is fixed and that you c

Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py

Updates: Status: Accepted Comment #1 on issue 1941 by brownian.box: Patch: Fixes to projecthosting_upload.py http://code.google.com/p/lilypond/issues/detail?id=1941 (No comment was entered for this change.) ___ bug-lilypond mailing list bu

Re: Issue 824 in lilypond: Enhancement: anchors in the music stream

Updates: Status: Verified Comment #17 on issue 824 by brownian.box: Enhancement: anchors in the music stream http://code.google.com/p/lilypond/issues/detail?id=824 (No comment was entered for this change.) ___ bug-lilypond mailing list bug

Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:'

Comment #4 on issue 1008 by brownian.box: Some warning/error messages are not prefixed with 'warning:'/'error:' http://code.google.com/p/lilypond/issues/detail?id=1008 Please, is there any code to test? `grep -r '(_' . | grep -vE 'error|warning'` shows a lot still.

Re: Issue 1193 in lilypond: Enhancement: internal ledger lines

Updates: Status: Verified Comment #31 on issue 1193 by brownian.box: Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lil

Re: Issue 1292 in lilypond: Enhancement: twelve-notation support

Updates: Status: Verified Comment #12 on issue 1292 by brownian.box: Enhancement: twelve-notation support http://code.google.com/p/lilypond/issues/detail?id=1292 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-l

Re: Issue 1301 in lilypond: Strange collision of note and clef

Updates: Status: Verified Comment #11 on issue 1301 by brownian.box: Strange collision of note and clef http://code.google.com/p/lilypond/issues/detail?id=1301 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lil

Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison

Updates: Status: Verified Comment #11 on issue 1529 by brownian.box: filename changing should not trigger a regtests comparison http://code.google.com/p/lilypond/issues/detail?id=1529 (No comment was entered for this change.) ___ bug-lilyp

Re: Issue 1795 in lilypond: Improve handling of languages in doc and website build

Updates: Status: Verified Comment #8 on issue 1795 by brownian.box: Improve handling of languages in doc and website build http://code.google.com/p/lilypond/issues/detail?id=1795 (No comment was entered for this change.) ___ bug-lilypond m

Re: Issue 1852 in lilypond: manuals needs more explicit dependencies

Comment #21 on issue 1852 by brownian.box: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 Please, why "Patch-needs_work"? Shouldn't it be removed? Please, if this is fixed, drop "fixed_X_Y_Z" here instead. Thanks!

Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly)

Updates: Status: Verified Comment #9 on issue 1868 by brownian.box: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1868 (No comment was entered for this change.)

Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties

Updates: Status: Verified Comment #8 on issue 1878 by brownian.box: Add support for custom ledger positions, using two new staff-symbol properties http://code.google.com/p/lilypond/issues/detail?id=1878 (No comment was entered for this change.) __

Re: Issue 1889 in lilypond: Lilypond-book: Improve options handling by processing everything in one place

Updates: Status: Verified Comment #6 on issue 1889 by brownian.box: Lilypond-book: Improve options handling by processing everything in one place http://code.google.com/p/lilypond/issues/detail?id=1889 (No comment was entered for this change.) ___

Re: Issue 1891 in lilypond: New alist to replace special characters

Updates: Status: Verified Comment #11 on issue 1891 by brownian.box: New alist to replace special characters http://code.google.com/p/lilypond/issues/detail?id=1891 (No comment was entered for this change.) ___ bug-lilypond mailing list bu

Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent

Updates: Status: Verified Comment #9 on issue 1893 by brownian.box: Terminates outside_staff_callback early if a grob is outside a slur's X-extent http://code.google.com/p/lilypond/issues/detail?id=1893 (No comment was entered for this change.) __

Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure

Updates: Status: Verified Labels: fixed_2_15_13 Comment #9 on issue 1905 by brownian.box: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure http://code.google.com/p/lilypond/issues/detail?id=1905 (No comment was entered for

Re: Issue 1909 in lilypond: Doc: add a note about \relative f to notation (Rietveld 5096046)

Updates: Status: Verified Comment #4 on issue 1909 by brownian.box: Doc: add a note about \relative f to notation (Rietveld 5096046) http://code.google.com/p/lilypond/issues/detail?id=1909 (No comment was entered for this change.) ___ bug-

Re: Issue 1914 in lilypond: Manual page break in a user defined variable

Updates: Status: Verified Comment #13 on issue 1914 by brownian.box: Manual page break in a user defined variable http://code.google.com/p/lilypond/issues/detail?id=1914 (No comment was entered for this change.) ___ bug-lilypond mailing li

Re: Issue 1920 in lilypond: arguments in docs don't alway agree

Updates: Status: Verified Comment #5 on issue 1920 by brownian.box: arguments in docs don't alway agree http://code.google.com/p/lilypond/issues/detail?id=1920 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lil

Re: Issue 1932 in lilypond: error: need \paper for paper block

Updates: Status: Verified Comment #5 on issue 1932 by brownian.box: error: need \paper for paper block http://code.google.com/p/lilypond/issues/detail?id=1932 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypon

Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1941 by mts...@gmail.com: Patch: Fixes to projecthosting_upload.py http://code.google.com/p/lilypond/issues/detail?id=1941 Fixes to projecthosting_upload.py http://codereview.appspot.com/5144045 _