Re: Issue 1987 in lilypond: Patch: Get rid of most of the insane string-tunings API

2011-10-23 Thread lilypond
Comment #3 on issue 1987 by percival.music...@gmail.com: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987 We don't really have a process. Bigger fish to fry at the moment. I definitely do not want a non-working master. If there

Issue 1989 in lilypond: Patch: Website: use external $LILYPOND_WEB_MEDIA_GIT

2011-10-23 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1989 by percival.music...@gmail.com: Patch: Website: use external $LILYPOND_WEB_MEDIA_GIT http://code.google.com/p/lilypond/issues/detail?id=1989 Website: use external $LILYPOND_WEB_MEDIA_GIT This builds the website using t

Re: Issue 1987 in lilypond: Patch: Get rid of most of the insane string-tunings API

2011-10-23 Thread lilypond
Comment #2 on issue 1987 by d...@gnu.org: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987 It uses much fewer #{ ... #} commands during initialization. And it just stores pitch lists instead of whole chords. Maybe storing the

Re: Issue 1986 in lilypond: Patch: Fixes slope errors from incorrect X extents in Beam::print.

2011-10-23 Thread m...@apollinemike.com
On Oct 24, 2011, at 6:01 AM, lilyp...@googlecode.com wrote: > Updates: > Labels: Patch-review > > Comment #2 on issue 1986 by percival.music...@gmail.com: Patch: Fixes slope > errors from incorrect X extents in Beam::print. > http://code.google.com/p/lilypond/issues/detail?id=1986#c2 > >

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

2011-10-23 Thread lilypond
Updates: Status: Fixed Comment #6 on issue 1927 by percival.music...@gmail.com: 2.15.2 doesn't build anymore on Mageia http://code.google.com/p/lilypond/issues/detail?id=1927 for clarity: I believe that the error posted here has been fixed in git master. If you see the same error,

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

2011-10-23 Thread lilypond
Comment #5 on issue 1927 by percival.music...@gmail.com: 2.15.2 doesn't build anymore on Mageia http://code.google.com/p/lilypond/issues/detail?id=1927 Then report those errors. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.

Re: Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (before running convert-ly)

2011-10-23 Thread lilypond
Comment #2 on issue 1988 by d...@gnu.org: Patch: Rename \markuplines to \markuplist (before running convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1988 A markup list exactly is _not_ lines. It is the state that has _not_ yet been turned into lines. When you use them as mar

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

2011-10-23 Thread lilypond
Comment #4 on issue 1927 by tho...@btspuhler.com: 2.15.2 doesn't build anymore on Mageia http://code.google.com/p/lilypond/issues/detail?id=1927 On Sunday, October 23, 2011 08:59:58 pm you wrote: What I mean is, when gcc is being upgraded it less forgiving and some warnings turn into erro

Re: nobody cares about LSR, part 2 (was: wrong alignment...)

2011-10-23 Thread -Eluze
hi again please don't push this snippet - the actual code is the code that produces the erroneous lyric placement with the actual (test-)version. the fantastic thing is that the output is correct in the LSR which uses version 2.12.2. i have investigated further and found the error occurs since 2

Re: Issue 1980 in lilypond: Patch: Sketch for in-notes.

2011-10-23 Thread lilypond
Updates: Labels: Patch-review Comment #5 on issue 1980 by percival.music...@gmail.com: Patch: Sketch for in-notes. http://code.google.com/p/lilypond/issues/detail?id=1980#c5 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-

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

2011-10-23 Thread lilypond
Comment #3 on issue 1927 by percival.music...@gmail.com: 2.15.2 doesn't build anymore on Mageia http://code.google.com/p/lilypond/issues/detail?id=1927 I believe the problem is one of build order, not gcc. I think that Julien has fixed this. Try git. ___

Re: Issue 1986 in lilypond: Patch: Fixes slope errors from incorrect X extents in Beam::print.

2011-10-23 Thread lilypond
Updates: Labels: Patch-review Comment #2 on issue 1986 by percival.music...@gmail.com: Patch: Fixes slope errors from incorrect X extents in Beam::print. http://code.google.com/p/lilypond/issues/detail?id=1986#c2 Patchy the autobot says: LGTM. Changed output in beam-consistent-brok

Re: Issue 1987 in lilypond: Patch: Get rid of most of the insane string-tunings API

2011-10-23 Thread lilypond
Updates: Labels: Patch-review Comment #1 on issue 1987 by percival.music...@gmail.com: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987#c1 Patchy the autobot says: LGTM. Memory cell count drops by up to 0.330\!

Re: Issue 1981 in lilypond: Patch: Adds Scheme function for spring constructor.

2011-10-23 Thread lilypond
Updates: Labels: Patch-review Comment #3 on issue 1981 by percival.music...@gmail.com: Patch: Adds Scheme function for spring constructor. http://code.google.com/p/lilypond/issues/detail?id=1981#c3 Patchy the autobot says: LGTM. ___ bug-li

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

2011-10-23 Thread lilypond
Comment #2 on issue 1927 by tho...@btspuhler.com: 2.15.2 doesn't build anymore on Mageia http://code.google.com/p/lilypond/issues/detail?id=1927 I wonder if someone had a chance to look at this. The last release that still built and still builds is 2.14.12. Distries are about to ugrade to t

Re: Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (before running convert-ly)

2011-10-23 Thread lilypond
Updates: Labels: -Patch-new Patch-needs_work Needs-evidence Comment #1 on issue 1988 by percival.music...@gmail.com: Patch: Rename \markuplines to \markuplist (before running convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1988 I don't like the idea of this. Yes, to a

Re: Issue 1979 in lilypond: Patch: convert-ly rules for Stem \#'stencil = \#\#f

2011-10-23 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #3 on issue 1979 by colinpkc...@gmail.com: Patch: convert-ly rules for Stem \#'stencil = \#\#f http://code.google.com/p/lilypond/issues/detail?id=1979 Counted down to 20111023 __

Re: Issue 1663 in lilypond: Images missing on web site

2011-10-23 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #53 on issue 1663 by colinpkc...@gmail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 Counted down to 20111023 ___ bug-lilypond mailing list bug

Re: Issue 1506 in lilypond: \tempo after StopStaff/StartStaff forces extension of staff symbol

2011-10-23 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #13 on issue 1506 by colinpkc...@gmail.com: \tempo after StopStaff/StartStaff forces extension of staff symbol http://code.google.com/p/lilypond/issues/detail?id=1506 Counted down to 20111023

Re: nobody cares about LSR, part 2 (was: wrong alignment...)

2011-10-23 Thread Graham Percival
On Sun, Oct 23, 2011 at 01:34:53PM +0100, Phil Holmes wrote: > - Original Message - From: "Graham Percival" > > >Yes. Either be patient, or wait for somebody to care about LSR. > > I normally do this on my "Bug squad" day - Sunday. Last week I did > quite a bit of squadding and forgot a

Re: Issue 1978 in lilypond: lily-guile updates and CG: "Scheme->C interface"

2011-10-23 Thread lilypond
Updates: Status: Fixed Labels: -Patch-push fixed_2_15_15 Comment #2 on issue 1978 by bordage@gmail.com: lily-guile updates and CG: "Scheme->C interface" http://code.google.com/p/lilypond/issues/detail?id=1978 Pushed as 6ee8c04678442855cb794d4598c056c15c42673b and b4a2cb2

Re: Issue 1986 in lilypond: Patch: Fixes slope errors from incorrect X extents in Beam::print.

2011-10-23 Thread lilypond
Comment #1 on issue 1986 by mts...@gmail.com: Patch: Fixes slope errors from incorrect X extents in Beam::print. http://code.google.com/p/lilypond/issues/detail?id=1986#c1 Fixes slope errors from incorrect X extents in Beam::print. http://codereview.appspot.com/5293060

Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (before running convert-ly)

2011-10-23 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1988 by d...@gnu.org: Patch: Rename \markuplines to \markuplist (before running convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1988 Rename \markuplines to \markuplist (before running convert-ly) This inconsi

Re: Issue 1984 in lilypond: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments.

2011-10-23 Thread lilypond
Comment #2 on issue 1984 by d...@gnu.org: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments. http://code.google.com/p/lilypond/issues/detail?id=1984 Pushed to dev/staging as cda3f6014feee11572a41e5d7ebf2151787d6d77 _

Issue 1987 in lilypond: Patch: Get rid of most of the insane string-tunings API

2011-10-23 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1987 by d...@gnu.org: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987 Get rid of most of the insane string-tunings API convert-ly rules and translations are st

Re: nobody cares about LSR, part 2 (was: wrong alignment...)

2011-10-23 Thread Phil Holmes
- Original Message - From: "Graham Percival" To: "-Eluze" ; Cc: Sent: Sunday, October 23, 2011 4:00 AM Subject: nobody cares about LSR, part 2 (was: wrong alignment...) On Sat, Oct 22, 2011 at 12:22:54PM -0700, -Eluze wrote: > 1) add a snippet to LSR showing this method. Make sure

Issue 1986 in lilypond: Patch: Fixes slope errors from incorrect X extents in Beam::print.

2011-10-23 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1986 by mts...@gmail.com: Patch: Fixes slope errors from incorrect X extents in Beam::print. http://code.google.com/p/lilypond/issues/detail?id=1986 Fixes slope errors from incorrect X extents in Beam::print. http://coderev

Re: Issue 1980 in lilypond: Patch: Sketch for in-notes.

2011-10-23 Thread lilypond
Updates: Labels: Patch-new Comment #4 on issue 1980 by mts...@gmail.com: Patch: Sketch for in-notes. http://code.google.com/p/lilypond/issues/detail?id=1980#c4 Sketch for in-notes. http://codereview.appspot.com/5293053 ___ bug-lilypond maili

Re: Issue 1981 in lilypond: Patch: Adds Scheme function for spring constructor.

2011-10-23 Thread lilypond
Updates: Labels: Patch-new Comment #2 on issue 1981 by mts...@gmail.com: Patch: Adds Scheme function for spring constructor. http://code.google.com/p/lilypond/issues/detail?id=1981#c2 Adds Scheme function for spring constructor. http://codereview.appspot.com/5306050 ___

Re: Issue 1972 in lilypond: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions

2011-10-23 Thread lilypond
Updates: Labels: Patch-review Comment #11 on issue 1972 by percival.music...@gmail.com: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions http://code.google.com/p/lilypond/issues/detail?id=1972#c11 Patchy the autobot says: LGTM. ___

Re: Issue 1984 in lilypond: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments.

2011-10-23 Thread lilypond
Updates: Labels: Patch-review Comment #1 on issue 1984 by percival.music...@gmail.com: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments. http://code.google.com/p/lilypond/issues/detail?id=1984#c1 Patchy the autobot says: LGTM.