Re: Issue 1951 in lilypond: Scripts collide with accidentals

Updates: Labels: -Patch-push Patch-needs_work Comment #11 on issue 1951 by mts...@gmail.com: Scripts collide with accidentals http://code.google.com/p/lilypond/issues/detail?id=1951 Neil had some comments on this patch, so I'm gonna work on it some more and post a new patch later to

Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc

Updates: Status: Fixed Comment #15 on issue 1844 by mts...@gmail.com: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc http://code.google.com/p/lilypond/issues/detail?id=1844 Fixed with e071fd8953f7391f206987c0b3dd3195f1727f1c. _

Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc

On Oct 19, 2011, at 4:03 AM, lilyp...@googlecode.com wrote: > > Comment #14 on issue 1844 by colinpkc...@gmail.com: Changes variable names in > include/beam-scoring-problem.hh and beam-quanting.cc > http://code.google.com/p/lilypond/issues/detail?id=1844 > > Does this still need work, Mike? Jam

Re: Issue 1948 in lilypond: Windows install clobbered system PATH

Comment #7 on issue 1948 by k-ohara5...@oco.net: Windows install clobbered system PATH http://code.google.com/p/lilypond/issues/detail?id=1948 If LilyPond still uses NSIS as its installer for Windows other software packages using NSIS had this problem.

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

Status: Accepted Owner: Labels: Type-Enhancement Patch-countdown New issue 1978 by percival.music...@gmail.com: lily-guile updates and CG: "Scheme->C interface" http://code.google.com/p/lilypond/issues/detail?id=1978 http://codereview.appspot.com/4917044/ __

Re: Issue 1917 in lilypond: Hyperlinks in web-big-page.html do not work

Updates: Labels: -Patch-review Patch-countdown Comment #7 on issue 1917 by percival.music...@gmail.com: Hyperlinks in web-big-page.html do not work http://code.google.com/p/lilypond/issues/detail?id=1917 (No comment was entered for this change.) _

Re: Issue 1952 in lilypond: Patch: Sketch for broken beams with consistent slopes

Updates: Labels: -Patch-review Patch-countdown Comment #6 on issue 1952 by percival.music...@gmail.com: Patch: Sketch for broken beams with consistent slopes http://code.google.com/p/lilypond/issues/detail?id=1952 (No comment was entered for this change.) ___

Re: Issue 1951 in lilypond: Scripts collide with accidentals

Updates: Labels: -Patch-countdown Patch-push Comment #10 on issue 1951 by percival.music...@gmail.com: Scripts collide with accidentals http://code.google.com/p/lilypond/issues/detail?id=1951 (No comment was entered for this change.) ___ b

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

Updates: Labels: -Patch-needs_work Patch-review Comment #51 on issue 1663 by percival.music...@gmail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 rietveld was being a pain about giving us the patch. It must be applied with this: git cl

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

Updates: Labels: Patch-review Comment #11 on issue 1506 by percival.music...@gmail.com: \tempo after StopStaff/StartStaff forces extension of staff symbol http://code.google.com/p/lilypond/issues/detail?id=1506#c11 Patchy the autobot says: LGTM. _

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

Updates: Labels: -Patch-review Patch-needs_work Comment #8 on issue 1972 by colinpkc...@gmail.com: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions http://code.google.com/p/lilypond/issues/detail?id=1972 Keith has mentioned some concerns and suggestions

Re: Issue 1957 in lilypond: Patch: Allows NoteColumns to be skipped over by glissandi.

Updates: Status: Fixed Labels: Fixed_2_15_15 Comment #6 on issue 1957 by colinpkc...@gmail.com: Patch: Allows NoteColumns to be skipped over by glissandi. http://code.google.com/p/lilypond/issues/detail?id=1957 I believe this was pushed as commit 60f4e610f5ffb3d5d1201fd5fa258c

Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc

Comment #14 on issue 1844 by colinpkc...@gmail.com: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc http://code.google.com/p/lilypond/issues/detail?id=1844 Does this still need work, Mike? James had some concerns on Rietveld. The patch has been on patch-push f

Re: Issue 1977 in lilypond: BarLine #'bar-extent wrongly documented as internal property

Comment #3 on issue 1977 by brownian@gmail.com: BarLine #'bar-extent wrongly documented as internal property http://code.google.com/p/lilypond/issues/detail?id=1977 sorry, 'bar-extent, not 'bar-size ___ bug-lilypond mailing list bug-lilypond@g

Re: Issue 1977 in lilypond: BarLine #'bar-extent wrongly documented as internal property

Comment #2 on issue 1977 by brownian@gmail.com: BarLine #'bar-extent wrongly documented as internal property http://code.google.com/p/lilypond/issues/detail?id=1977 I believe that internal can not be set by user (as 'use-breve-rest could not be set while being in internal use, see Issue

Re: Issue 1977 in lilypond: BarLine #'bar-extent wrongly documented as internal property

Comment #1 on issue 1977 by pkx1...@gmail.com: BarLine #'bar-extent wrongly documented as internal property http://code.google.com/p/lilypond/issues/detail?id=1977 What should it be: 'User settable properties' ? ___ bug-lilypond mailing list bug

Issue 1977 in lilypond: BarLine #'bar-extent wrongly documented as internal property

Status: Accepted Owner: Labels: Type-Documentation New issue 1977 by brownian@gmail.com: BarLine #'bar-extent wrongly documented as internal property http://code.google.com/p/lilypond/issues/detail?id=1977 \version "2.15.14" \relative c'' { \override Staff.BarLine #'bar-extent = #

Re: Issue 1962 in lilypond: Visible gap in span bar when making lyrics to avoid bar lines

Comment #6 on issue 1962 by brownian@gmail.com: Visible gap in span bar when making lyrics to avoid bar lines http://code.google.com/p/lilypond/issues/detail?id=1962 Thank you, Neil. For me --- it seems to work as "desired" after adding these lines to Lyrics context: \override BarLine

Re: Issue 1962 in lilypond: Visible gap in span bar when making lyrics to avoid bar lines

Comment #5 on issue 1962 by n.putt...@gmail.com: Visible gap in span bar when making lyrics to avoid bar lines http://code.google.com/p/lilypond/issues/detail?id=1962 LSR 648 changes the height to two spaces and moves it up a space. This does the same, without having to use extra-offset: \o

Re: Issue 1953 in lilypond: Removes closeness-factor from the Slur details list

Updates: Status: Fixed Comment #7 on issue 1953 by mts...@gmail.com: Removes closeness-factor from the Slur details list http://code.google.com/p/lilypond/issues/detail?id=1953 Fixed with 5f280a566ed2ec0f1b361d9c4ce08456e9eab9d0. ___ bug-l

Re: Issue 1953 in lilypond: Removes closeness-factor from the Slur details list

Comment #6 on issue 1953 by bordage@gmail.com: Removes closeness-factor from the Slur details list http://code.google.com/p/lilypond/issues/detail?id=1953 Mike, could you close this issue and your codereview issue, since you already pushed the patch as 5f280a566ed2ec0f1b361d9c4ce08456e9

Re: Issue 1926 in lilypond: 2.15.12 processing speed problems

Updates: Status: Fixed Labels: -Patch-push fixed_2_15_15 Comment #23 on issue 1926 by bordage@gmail.com: 2.15.12 processing speed problems http://code.google.com/p/lilypond/issues/detail?id=1926 Pushed as 8adeb99e344bf047b9b3b9b48a9e97e59e8fc4d3.

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

Comment #10 on issue 1506 by mts...@gmail.com: \tempo after StopStaff/StartStaff forces extension of staff symbol http://code.google.com/p/lilypond/issues/detail?id=1506 Hey all, As I've now used this patch for every piece I've written for the past couple months, I've decided to shepherd i

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

Updates: Labels: Patch-new Comment #9 on issue 1506 by mts...@gmail.com: \tempo after StopStaff/StartStaff forces extension of staff symbol http://code.google.com/p/lilypond/issues/detail?id=1506#c9 Fixes issue 1506 (overhang of staff symbol). http://codereview.appspot.com/5303043

Re: Issue 1962 in lilypond: Visible gap in span bar when making lyrics to avoid bar lines

Comment #4 on issue 1962 by brownian@gmail.com: Visible gap in span bar when making lyrics to avoid bar lines http://code.google.com/p/lilypond/issues/detail?id=1962 Well, i've finally understood, that this is barline itself ,) Barline's visibility in lyrics is a feature, not a bug: ht

Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax

Comment #21 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord with \relative and #{ #} syntax http://code.google.com/p/lilypond/issues/detail?id=1110 The approach outlined in the patch will about double the effort for relativizing music when done correctly. In my opinion, it

Re: Issue 1526 in lilypond: Building only English docs

Comment #15 on issue 1526 by julien.r...@gmail.com: Building only English docs http://code.google.com/p/lilypond/issues/detail?id=1526 The long time is because your build system is half broken, as I said: you need proper dependencies on targets, and a proper separation of targets. At the

Re: Issue 1567 in lilypond: Add documentation for footnotes

On Oct 18, 2011, at 12:38 PM, lilyp...@googlecode.com wrote: > > Comment #13 on issue 1567 by pkx1...@gmail.com: Add documentation for > footnotes > http://code.google.com/p/lilypond/issues/detail?id=1567 > > I'm making headway into documenting the auto and (I prefer) manual > footnote commands

Re: Issue 1567 in lilypond: Add documentation for footnotes

Comment #13 on issue 1567 by pkx1...@gmail.com: Add documentation for footnotes http://code.google.com/p/lilypond/issues/detail?id=1567 I'm making headway into documenting the auto and (I prefer) manual footnote commands. However, I'm coming across something I don't understand why it doesn't

Re: Issue 1975 in lilypond: VerticalAxisGroup staff-staff-spacing gets insane spring distances

Updates: Status: Fixed Comment #3 on issue 1975 by mts...@gmail.com: VerticalAxisGroup staff-staff-spacing gets insane spring distances http://code.google.com/p/lilypond/issues/detail?id=1975 Fixed with d6bc972f8a6492ac5b94ffea17823a865e31b21a. __

Re: Issue 1976 in lilypond: Patch: Handle quartertone pitch differences in fingering calculations.

Updates: Labels: -Patch-new Patch-abandoned Comment #1 on issue 1976 by d...@gnu.org: Patch: Handle quartertone pitch differences in fingering calculations. http://code.google.com/p/lilypond/issues/detail?id=1976 Issue 1753 is related but different. _

Issue 1976 in lilypond: Patch: Handle quartertone pitch differences in fingering calculations.

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1976 by d...@gnu.org: Patch: Handle quartertone pitch differences in fingering calculations. http://code.google.com/p/lilypond/issues/detail?id=1976 Handle quartertone pitch differences in fingering calculations. Intended a

Re: Issue 1975 in lilypond: VerticalAxisGroup staff-staff-spacing gets insane spring distances

Comment #2 on issue 1975 by mts...@gmail.com: VerticalAxisGroup staff-staff-spacing gets insane spring distances http://code.google.com/p/lilypond/issues/detail?id=1975 The problem comes from a division by 0 error in bar-line.cc (when staff radius is 0, calc_bar_extent goes berserk). I am

Re: Issue 1526 in lilypond: Building only English docs

I should clarify that I don't like doc-section.sh, I've never liked it; it's the worst kind of "alternate build system" hack... but mao, just look at those numbers. 3 minutes vs. less than 1 second ?! I hadn't realized the difference was that extreme. I'm sorely tempted to spend some time

Re: Issue 1975 in lilypond: VerticalAxisGroup staff-staff-spacing gets insane spring distances

Comment #1 on issue 1975 by mts...@gmail.com: VerticalAxisGroup staff-staff-spacing gets insane spring distances http://code.google.com/p/lilypond/issues/detail?id=1975 git bisect reports that this is the commit where the change occurs: b92ea16ef75d8aaa7bdb9f492b58d7af906e7945 is the first b

Issue 1975 in lilypond: VerticalAxisGroup staff-staff-spacing gets insane spring distances

Status: New Owner: mts...@gmail.com Labels: Type-Critical New issue 1975 by mts...@gmail.com: VerticalAxisGroup staff-staff-spacing gets insane spring distances http://code.google.com/p/lilypond/issues/detail?id=1975 In the snippet below, there's a line to comment in and out to see a regres