headers
lilypond | 1 Jul 2011 03:21

Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655

Updates:
	Status: Started
	Owner: Carl.D.S... <at> gmail.com

Comment #9 on issue 1716 by Carl.D.S... <at> gmail.com: No convert-ly rule for  
the fix for issue 1655
http://code.google.com/p/lilypond/issues/detail?id=1716

I totally agree with "No backport of 1655" as that was a syntax change.

I'm not sure I agree about no convert-ly rule in 2.15, which was the  
genesis of this question.

Neil argues against a convert-ly rule; James and Reinhold (and I think I)  
argue in favor of a NOT_SMART convert-ly rule for any deleted syntax, even  
if it *is* an internal property.

I believe that adding a convert-ly rule would prevent somebody later coming  
back and adding a Critical Regression.

Since I haven't heard anybody say we *shouldn't* add a NOT_SMART rule, just  
that we *don't need to* add a NOT_SMART rule, I will go ahead and add a  
NOT_SMART rule unless I hear well-reasoned complaints.

But I won't backport to 2.14.
Permalink | Reply | 0 comments |
headers
lilypond | 1 Jul 2011 04:21

Issue 1727 in lilypond: Adds glissando stems to lilypond

Status: Accepted
Owner: mts... <at> gmail.com
Labels: Type-Enhancement Patch-review Priority-Medium

New issue 1727 by ColinPKC... <at> gmail.com: Adds glissando stems to lilypond
http://code.google.com/p/lilypond/issues/detail?id=1727

Proposed by Mike Solomon.

Patchset on Reitveld at http://codereview.appspot.com/4661061/

This issue added for tracking purposes
Permalink | Reply | 2 comments |
headers
lilypond | 1 Jul 2011 04:28

Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi

Status: Accepted
Owner: mts... <at> gmail.com
Labels: Type-Enhancement Priority-Medium Patch-review

New issue 1728 by ColinPKC... <at> gmail.com: Implements multi-line non-cross  
staff glissandi
http://code.google.com/p/lilypond/issues/detail?id=1728

Proposed by Mike Solomon:

Patch on Reitveld at http://codereview.appspot.com/4527086/
Permalink | Reply | 9 comments |
headers
lilypond | 1 Jul 2011 04:34

Issue 1729 in lilypond: Set spanner length as a spanner property

Status: Accepted
Owner: mts... <at> gmail.com
Labels: Type-Enhancement Priority-Medium Patch-review

New issue 1729 by ColinPKC... <at> gmail.com: Set spanner length as a spanner  
property
http://code.google.com/p/lilypond/issues/detail?id=1729

Proposed by Mike Solomon
Patcset on Reitveld at http://codereview.appspot.com/4641085/
Permalink | Reply | 2 comments |
headers
lilypond | 1 Jul 2011 11:39

Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi

Updates:
	Status: Fixed

Comment #1 on issue 1728 by mts... <at> gmail.com: Implements multi-line  
non-cross staff glissandi
http://code.google.com/p/lilypond/issues/detail?id=1728

Thanks for the comments & regtest checking.
Pushed as 4e55f40a1bf65633fedc62d09d91d8e3c0247efe.

Cheers,
MS
Permalink | Reply | 0 comments |
headers
lilypond | 1 Jul 2011 11:49

Re: Issue 1729 in lilypond: Set spanner length as a spanner property

Updates:
	Labels: -Patch-review Patch-needs_work

Comment #1 on issue 1729 by pkx1... <at> gmail.com: Set spanner length as a  
spanner property
http://code.google.com/p/lilypond/issues/detail?id=1729

 From mike:

--snip--

"...I have a version of this written in Scheme that I use in my graphical  
notation.
I'll throw up a new patch with this in the not-too-distant future.  ..."
Permalink | Reply | 0 comments |
headers
lilypond | 1 Jul 2011 11:28

Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655


Comment #10 on issue 1716 by percival.music.ca: No convert-ly rule for the  
fix for issue 1655
http://code.google.com/p/lilypond/issues/detail?id=1716

My apologies; I completely misunderstood the discussion.  Thanks for the  
summary, and I agree with your view.
Permalink | Reply | 0 comments |
headers
lilypond | 1 Jul 2011 19:49

Re: Issue 1706 in lilypond: Beaming causes lilypond to crash


Comment #7 on issue 1706 by n.putt... <at> gmail.com: Beaming causes lilypond to  
crash
http://code.google.com/p/lilypond/issues/detail?id=1706

Anybody else getting beam-skip.ly showing up in every regtest comparison?   
I assume it's not showing up between builds since they aren't compiled with  
disable-optimising:

 <at>  <at>  -173,6 +173,11  <at>  <at> 
               r2 r4 r8 f,
  programming error: Grob direction requested while calculation in progress.
  continuing, cross fingers
+beam-skip.ly:11:16: programming error: cyclic dependency:  
calculation-in-progress encountered for #'direction (Stem)
+  \clef bass r2
+                r4 r8 f,
+programming error: Grob direction requested while calculation in progress.
+continuing, cross fingers
  beam-skip.ly:13:13: programming error: cyclic dependency:  
calculation-in-progress encountered for #'direction (Stem)
    r4 f, 8 r8
               r2
 <at>  <at>  -181,11 +186,6  <at>  <at> 
  beam-skip.ly:12:5: programming error: cyclic dependency:  
calculation-in-progress encountered for #'direction (Stem)
    r2
       r4 g,8 r
-programming error: Grob direction requested while calculation in progress.
-continuing, cross fingers
(Continue reading)

Permalink | Reply | 0 comments |
headers
lilypond | 2 Jul 2011 01:20

Re: Issue 1726 in lilypond: python versions might not be updating


Comment #1 on issue 1726 by ColinPKC... <at> gmail.com: python versions might  
not be updating
http://code.google.com/p/lilypond/issues/detail?id=1726

Confirmed with the test above: scripts in /build/scripts/out receive the  
test version number, which is not changed on a subsequent make.
Permalink | Reply | 0 comments |
headers
lilypond | 2 Jul 2011 01:51

Re: Issue 1726 in lilypond: python versions might not be updating


Comment #2 on issue 1726 by percival.music.ca: python versions might not be  
updating
http://code.google.com/p/lilypond/issues/detail?id=1726

ok.  Next test (not necessarily from Colin) is to confirm that it was  
working recently.

first, do:
   git checkout release-2.15.1-1
second, do the same test as above.
Permalink | Reply | 0 comments |

Gmane