Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions

Updates: Status: Started Labels: -fixed_2_15_14 Comment #14 on issue 1321 by k-ohara5...@oco.net: Enhancement: add partcombineUp and partcombineDown functions http://code.google.com/p/lilypond/issues/detail?id=1321 Probably best to keep this as a 'Started' enhancement request,

Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals

Updates: Status: Verified Labels: -fixed_2_15_4 -fixed_2_14_2 -backport fixed_2_15_15 Comment #23 on issue 1701 by k-ohara5...@oco.net: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 Since there is nothing to b

Re: Issue 1990 in lilypond: Patch: Uses convert-ly to update changes stemming from the creation of a Flag grob.

Updates: Labels: Patch-review Comment #1 on issue 1990 by percival.music...@gmail.com: Patch: Uses convert-ly to update changes stemming from the creation of a Flag grob. http://code.google.com/p/lilypond/issues/detail?id=1990#c1 Patchy the autobot says: LGTM. __

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

Updates: Labels: Patch-review Comment #9 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#c9 Patchy the autobot says: LGTM. ___ bu

Re: Issue 1127 in lilypond: Piano staff centred dynamics

Comment #6 on issue 1127 by lemzw...@gmail.com: Piano staff centred dynamics http://code.google.com/p/lilypond/issues/detail?id=1127 Your second system looks almost perfect, Keith! And the vertical position of the blue p looks good also. The only remaining issue (not covered with the secon

Issue 1991 in lilypond: Improve vertical positioning of 'loose' lines: Lyrics, Dynamics,

Status: Accepted Owner: Labels: Type-Enhancement New issue 1991 by k-ohara5...@oco.net: Improve vertical positioning of 'loose' lines: Lyrics, Dynamics, http://code.google.com/p/lilypond/issues/detail?id=1991 Notes and articulations sometimes project through lines of Lyrics or Dynamics

Re: \override Beam #'consistent-slope = ##t should be default

There are lots of broken beams in Scriabin's first prelude The original publisher makes no attempt at consistent slopes. Peters Edition prints nearly-equal slopes across the line-breaks, but lets the beam height There is a Lilypond

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

Comment #14 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 hmm. I rewrote Patchy to raise exceptions about 24 hours ago, instead of relying on manually re

Re: Issue 1968 in lilypond: test full GUB rebuild

Updates: Status: Fixed Labels: fixed_2_15_15 Comment #5 on issue 1968 by percival.music...@gmail.com: test full GUB rebuild http://code.google.com/p/lilypond/issues/detail?id=1968 rebuild went ok with gub 634fd7f67f0c04d0a3e8dfb2e9dd945a08ae3a4b ; or at least, it was able to

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

Comment #13 on issue 1972 by k-ohara5...@oco.net: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions http://code.google.com/p/lilypond/issues/detail?id=1972 Patchy the autobot said "LGTM" about a patch that doesn't compile. But the error was trivial, and the fix

Re: Issue 1127 in lilypond: Piano staff centred dynamics

Comment #5 on issue 1127 by k-ohara5...@oco.net: Piano staff centred dynamics http://code.google.com/p/lilypond/issues/detail?id=1127 This is confusing. Let's use pictures. Comment 1 (part 2a) says to spread the staves if centered dynamics hit either skyline, which I interpret as line 1 in

Re: Issue 1974 in lilypond: Fix the 404 on contributor-big-page and contributor/website-build

Updates: Status: Fixed Labels: -Patch-push fixed_2_15_15 Comment #4 on issue 1974 by percival.music...@gmail.com: Fix the 404 on contributor-big-page and contributor/website-build http://code.google.com/p/lilypond/issues/detail?id=1974 c18a564a424c0469ef735c6866a2d88e4d85481d

Re: Issue 983 in lilypond: relative location of css/ and pictures/ dir

Updates: Status: Fixed Labels: -Priority-High -Patch-push fixed_2_15_15 Comment #6 on issue 983 by percival.music...@gmail.com: relative location of css/ and pictures/ dir http://code.google.com/p/lilypond/issues/detail?id=983 7a5ed5ba18cd1b11b9468e6e6d45ab1c8987923a ___

Issue 1990 in lilypond: Patch: Uses convert-ly to update changes stemming from the creation of a Flag grob.

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1990 by mts...@gmail.com: Patch: Uses convert-ly to update changes stemming from the creation of a Flag grob. http://code.google.com/p/lilypond/issues/detail?id=1990 Uses convert-ly to update changes stemming from the creati

Re: MetronomeMark #'break-align-symbols sometimes fails

On 14 October 2011 00:33, Kieren MacMillan wrote: > > This is a little frustrating, as it was part of a bounty fix from some > time ago. > > I understand the ultimate fix is [apparently] difficult — and Neil > generously gave me a hack to tweak certain issues, especially at line > breaks — but it

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

Comment #8 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 Convert rules are there. I'd like to rename the property stringTunings to stringTuning, but that can be left to a later patch/convert ru

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

Updates: Labels: Patch-new Comment #7 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#c7 Get rid of most of the insane string-tunings API convert-ly rules and translations are still missing

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

Comment #54 on issue 1663 by julien.r...@gmail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 For the record, in reply to Comment 51: Rietvield was not the issue. Rietvield was merely providing the .patch file created by git. Git uses `diff --git'

Re: Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests

Updates: Labels: -Patch-needs_work Patch-new Comment #11 on issue 814 by reinhold...@gmail.com: warning-as-error should be enabled when compiling the regtests http://code.google.com/p/lilypond/issues/detail?id=814 Here's a patch that fixes the warning-as-error handling described in

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

Comment #6 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 I am just writing the convert-ly rules. I noticed that the context property is called stringTunings, but the commands I replace with \

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

Comment #5 on issue 1987 by reinhold...@gmail.com: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987 Am Monday, 24. October 2011, 08:38:09 schrieb lilyp...@googlecode.com: I still don't quite get the process regarding convert-ly ru

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

Updates: Labels: Needs-evidence Comment #7 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 I don't know what to do with this issue. Probably, this should be "doc" issue. Pr

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

Comment #4 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 @Graham: you marked this as Needs_evidence. Please compile the following file written in current syntax and look at its ou

Re: Issue 1949 in lilypond: add to paper.scm 6 x 9 in

Updates: Status: Accepted Comment #2 on issue 1949 by brownian@gmail.com: add to paper.scm 6 x 9 in http://code.google.com/p/lilypond/issues/detail?id=1949 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lil

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

Updates: Status: Accepted Comment #2 on issue 1976 by brownian@gmail.com: Patch: Handle quartertone pitch differences in fingering calculations. http://code.google.com/p/lilypond/issues/detail?id=1976 (No comment was entered for this change.)

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

Updates: Status: Accepted Comment #4 on issue 1979 by brownian@gmail.com: Patch: convert-ly rules for Stem \#'stencil = \#\#f http://code.google.com/p/lilypond/issues/detail?id=1979 (No comment was entered for this change.) ___ bug-lil

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

Updates: Status: Accepted Comment #6 on issue 1980 by brownian@gmail.com: Patch: Sketch for in-notes. http://code.google.com/p/lilypond/issues/detail?id=1980 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-l

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

Updates: Status: Accepted Comment #4 on issue 1981 by brownian@gmail.com: Patch: Adds Scheme function for spring constructor. http://code.google.com/p/lilypond/issues/detail?id=1981 (No comment was entered for this change.) ___ bug-lil

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

Updates: Status: Accepted Comment #4 on issue 1984 by brownian@gmail.com: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments. http://code.google.com/p/lilypond/issues/detail?id=1984 (No comment was entered for this change.) _

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

Updates: Status: Accepted Comment #3 on issue 1986 by brownian@gmail.com: Patch: Fixes slope errors from incorrect X extents in Beam::print. http://code.google.com/p/lilypond/issues/detail?id=1986 (No comment was entered for this change.)

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

Updates: Status: Accepted Comment #4 on issue 1987 by brownian@gmail.com: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987 (No comment was entered for this change.) ___ bug

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

Updates: Status: Accepted Comment #3 on issue 1988 by brownian@gmail.com: Patch: Rename \markuplines to \markuplist (before running convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1988 (No comment was entered for this change.) _

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

Updates: Status: Accepted Comment #1 on issue 1989 by brownian@gmail.com: Patch: Website: use external $LILYPOND_WEB_MEDIA_GIT http://code.google.com/p/lilypond/issues/detail?id=1989 (No comment was entered for this change.) ___ bug-li