Issue 2290 in lilypond: Patch: Gets rid of beam stencil command

2012-02-05 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2290 by mts...@gmail.com: Patch: Gets rid of beam stencil command http://code.google.com/p/lilypond/issues/detail?id=2290 Gets rid of beam stencil command http://codereview.appspot.com/5636047 ___

Re: Issue 2148 in lilypond: vertical skylines should use stencil integrals

2012-02-05 Thread lilypond
Comment #16 on issue 2148 by mts...@gmail.com: vertical skylines should use stencil integrals http://code.google.com/p/lilypond/issues/detail?id=2148#c16 Gets vertical skylines from grob stencils http://codereview.appspot.com/5626052 ___ bug-lily

Re: Issue 2288 in lilypond: Patch: Deprecates dashed-slur stencil

2012-02-05 Thread lilypond
Comment #2 on issue 2288 by m...@apollinemike.com: Patch: Deprecates dashed-slur stencil http://code.google.com/p/lilypond/issues/detail?id=2288 1) The dashed-slur stencil is not used for the documented ways to make dashed slurs. 2) This patch completely removes dashed-slur, as opposed to m

Issue 2289 in lilypond: repeat percent with skips can crash

2012-02-05 Thread lilypond
Status: Accepted Owner: Labels: Type-Critical Regression New issue 2289 by k-ohara5...@oco.net: repeat percent with skips can crash http://code.google.com/p/lilypond/issues/detail?id=2289 The method of LSR 473 to make measure counters (see issue 146) aa = \repeat percent 5 s2. \addQuote

Re: Issue 2276 in lilypond: multiple stanzas chord symbols collide with staff

2012-02-05 Thread lilypond
Updates: Labels: -Patch-push Patch-countdown Comment #12 on issue 2276 by k-ohara5...@oco.net: multiple stanzas chord symbols collide with staff http://code.google.com/p/lilypond/issues/detail?id=2276 (No comment was entered for this change.)

Re: Issue 2276 in lilypond: multiple stanzas chord symbols collide with staff

2012-02-05 Thread lilypond
Updates: Labels: -Patch-review Patch-push Comment #11 on issue 2276 by k-ohara5...@oco.net: multiple stanzas chord symbols collide with staff http://code.google.com/p/lilypond/issues/detail?id=2276 My comments were in case somebody else adopts the patch. It is good to go so far as

Re: Issue 2276 in lilypond: multiple stanzas chord symbols collide with staff

2012-02-05 Thread lilypond
Comment #10 on issue 2276 by colinpkc...@gmail.com: multiple stanzas chord symbols collide with staff http://code.google.com/p/lilypond/issues/detail?id=2276 @Keith: Do your comments on Rietveld mean you still want to work on this, and so it should be set to "needs work"? If you would like

Re: Issue 2275 in lilypond: Patch: Doc: simplify example for unpure-pure containers

2012-02-05 Thread lilypond
Updates: Labels: -Patch-countdown Patch-needs_work Comment #4 on issue 2275 by colinpkc...@gmail.com: Patch: Doc: simplify example for unpure-pure containers http://code.google.com/p/lilypond/issues/detail?id=2275 Per discussion on Rietveld, this needs work _

Re: Issue 1461 in lilypond: Unexpected behavior of pitchedTrill within tablature

2012-02-05 Thread lilypond
20120205, please push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 451 in lilypond: Enhancement: a more flexible \parallelMusic syntax when used with \relative

2012-02-05 Thread lilypond
Comment #8 on issue 451 by colinpkc...@gmail.com: Enhancement: a more flexible \parallelMusic syntax when used with \relative http://code.google.com/p/lilypond/issues/detail?id=451 Counted down to 20120205, please push. ___ bug-lilypond mailing

Re: Issue 1461 in lilypond: Unexpected behavior of pitchedTrill within tablature

2012-02-05 Thread lilypond
Updates: Owner: d...@gnu.org Labels: -Patch-countdown Patch-needs_work Comment #6 on issue 1461 by colinpkc...@gmail.com: Unexpected behavior of pitchedTrill within tablature http://code.google.com/p/lilypond/issues/detail?id=1461 Per discussion on Rietveld, and implied by the

Re: Issue 2288 in lilypond: Patch: Deprecates dashed-slur stencil

2012-02-05 Thread lilypond
Updates: Labels: -Type-Enhancement Type-Patch Comment #1 on issue 2288 by k-ohara5...@oco.net: Patch: Deprecates dashed-slur stencil http://code.google.com/p/lilypond/issues/detail?id=2288 This needs some explanation. As I understand 1) The dashed-slur stencil is not used for the doc

Re: Issue 2276 in lilypond: multiple stanzas chord symbols collide with staff

2012-02-05 Thread lilypond
Comment #9 on issue 2276 by k-ohara5...@oco.net: multiple stanzas chord symbols collide with staff http://code.google.com/p/lilypond/issues/detail?id=2276 Patch at http://codereview.appspot.com/5624055/ changes no regression test output, but modifies one regression test to catch this issue

Re: Issue 2287 in lilypond: lyrics spaced too far from staff

2012-02-05 Thread lilypond
Updates: Status: Invalid Comment #1 on issue 2287 by mts...@gmail.com: lyrics spaced too far from staff http://code.google.com/p/lilypond/issues/detail?id=2287 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lil

Issue 2288 in lilypond: Patch: Deprecates dashed-slur stencil

2012-02-05 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2288 by mts...@gmail.com: Patch: Deprecates dashed-slur stencil http://code.google.com/p/lilypond/issues/detail?id=2288 Deprecates dashed-slur stencil http://codereview.appspot.com/5634044 ___

Re: Issue 2287 in lilypond: lyrics spaced too far from staff

2012-02-05 Thread -Eluze
lilypond-4 wrote: > > Status: Accepted > Owner: > Labels: Type-Critical > > New issue 2287 by mts...@gmail.com: lyrics spaced too far from staff > http://code.google.com/p/lilypond/issues/detail?id=2287 > > \version "2.15.28" > \new Staff \relative c'' { \override Stem #'direction = #DOWN

Re: Issue 2148 in lilypond: vertical skylines should use stencil integrals

2012-02-05 Thread lilypond
Comment #15 on issue 2148 by mts...@gmail.com: vertical skylines should use stencil integrals http://code.google.com/p/lilypond/issues/detail?id=2148 Gets vertical skylines from grob stencils http://codereview.appspot.com/5626052 ___ bug-lilypond

Issue 2287 in lilypond: lyrics spaced too far from staff

2012-02-05 Thread lilypond
Status: Accepted Owner: Labels: Type-Critical New issue 2287 by mts...@gmail.com: lyrics spaced too far from staff http://code.google.com/p/lilypond/issues/detail?id=2287 \version "2.15.28" \new Staff \relative c'' { \override Stem #'direction = #DOWN a2 a a a } \new Lyrics \lyricmode { la

Issue 2286 in lilypond: Patch: Make #{ c' #} and x=c' create a pitch instead of a NoteEvent

2012-02-05 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2286 by d...@gnu.org: Patch: Make #{ c' #} and x=c' create a pitch instead of a NoteEvent http://code.google.com/p/lilypond/issues/detail?id=2286 Make #{ c' #} and x=c' create a pitch instead of a NoteEvent Since the specif

Re: Issue 2148 in lilypond: vertical skylines should use stencil integrals

2012-02-05 Thread lilypond
Updates: Summary: vertical skylines should use stencil integrals Comment #14 on issue 2148 by mts...@gmail.com: vertical skylines should use stencil integrals http://code.google.com/p/lilypond/issues/detail?id=2148 I've done all of this merging so that we can resort these issues based

Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular

2012-02-05 Thread lilypond
Updates: Labels: Patch-new Comment #13 on issue 2148 by mts...@gmail.com: object outlines shouldn't be rectangular http://code.google.com/p/lilypond/issues/detail?id=2148#c13 Gets vertical skylines from grob stencils http://codereview.appspot.com/5626052 ___

Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular

2012-02-05 Thread lilypond
Comment #12 on issue 2148 by mts...@gmail.com: object outlines shouldn't be rectangular http://code.google.com/p/lilypond/issues/detail?id=2148 Issue 584 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://l

Re: Issue 584 in lilypond: Outside-staff placement of hairpins is 'too approximate'

2012-02-05 Thread lilypond
Updates: Status: Duplicate Mergedinto: 2148 Comment #3 on issue 584 by mts...@gmail.com: Outside-staff placement of hairpins is 'too approximate' http://code.google.com/p/lilypond/issues/detail?id=584 (No comment was entered for this change.)

Re: Issue 651 in lilypond: Volta bracket placed too high after a line break

2012-02-05 Thread lilypond
Updates: Status: Duplicate Mergedinto: 2148 Comment #5 on issue 651 by mts...@gmail.com: Volta bracket placed too high after a line break http://code.google.com/p/lilypond/issues/detail?id=651 I'm going to merge this and 650 into 2148 - if you think that volta brackets shou

Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular

2012-02-05 Thread lilypond
Comment #11 on issue 2148 by mts...@gmail.com: object outlines shouldn't be rectangular http://code.google.com/p/lilypond/issues/detail?id=2148 Issue 651 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://l

Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular

2012-02-05 Thread lilypond
Comment #10 on issue 2148 by mts...@gmail.com: object outlines shouldn't be rectangular http://code.google.com/p/lilypond/issues/detail?id=2148 Issue 650 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://l

Re: Issue 650 in lilypond: Broken hairpin placed too high after a line break

2012-02-05 Thread lilypond
Updates: Status: Duplicate Mergedinto: 2148 Comment #6 on issue 650 by mts...@gmail.com: Broken hairpin placed too high after a line break http://code.google.com/p/lilypond/issues/detail?id=650 (No comment was entered for this change.) ___

Re: Issue 650 in lilypond: Broken hairpin placed too high after a line break

2012-02-05 Thread lilypond
Comment #5 on issue 650 by mts...@gmail.com: Broken hairpin placed too high after a line break http://code.google.com/p/lilypond/issues/detail?id=650 Issue 1097 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org ht

Re: Issue 1097 in lilypond: better skylines for volta brackets

2012-02-05 Thread lilypond
Updates: Status: Duplicate Mergedinto: 650 Comment #11 on issue 1097 by mts...@gmail.com: better skylines for volta brackets http://code.google.com/p/lilypond/issues/detail?id=1097 (No comment was entered for this change.) ___ bug-

Re: Issue 650 in lilypond: Broken hairpin placed too high after a line break

2012-02-05 Thread lilypond
Updates: Labels: Patch-new Comment #4 on issue 650 by mts...@gmail.com: Broken hairpin placed too high after a line break http://code.google.com/p/lilypond/issues/detail?id=650#c4 Gets vertical skylines from grob stencils http://codereview.appspot.com/5626052 __

Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch

2012-02-05 Thread lilypond
Comment #30 on issue 2092 by gra...@percival-music.ca: lily-git.tcl should using a "working" branch http://code.google.com/p/lilypond/issues/detail?id=2092 ok. In case you missed the brief discussion on -devel, I think we want to switch to using git clone for everybody -- i.e. no more sp

Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC

2012-02-05 Thread lilypond
Comment #5 on issue 2271 by gra...@percival-music.ca: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 if somebody sends me a patch for GUB, I can apply that pretty much instantly. Then it can either wait until the next regular release, or I coul

Re: Issue 1985 in lilypond: musicxml2ly: group-symbol none leads to bus error

2012-02-05 Thread lilypond
Updates: Status: Verified Comment #7 on issue 1985 by philehol...@gmail.com: musicxml2ly: group-symbol none leads to bus error http://code.google.com/p/lilypond/issues/detail?id=1985 Confirmed fixed running musicxml2ly from 2.15.28 against that test file. ___

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

2012-02-05 Thread lilypond
Updates: Status: Verified Comment #8 on issue 1726 by philehol...@gmail.com: python versions might not be updating http://code.google.com/p/lilypond/issues/detail?id=1726 Verified as fixed - slightly different from above. make; make doc. Confirm lilylib.py has version 2.15.29. Ch

Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC

2012-02-05 Thread lilypond
Comment #4 on issue 2271 by d...@gnu.org: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 Who is going to do the actual work? If we don't have more than a fuzzy "developers should do it", this is not going to happen. This involves changing the resp

Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch

2012-02-05 Thread lilypond
Updates: Labels: -Patch-push Patch-needs_work Comment #29 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should using a "working" branch http://code.google.com/p/lilypond/issues/detail?id=2092 Janek identified some potential errors in the git usage with translation. I'm review

Re: Issue 650 in lilypond: Broken hairpin placed too high after a line break

2012-02-05 Thread lilypond
Updates: Labels: Patch-review Comment #3 on issue 650 by d...@gnu.org: Broken hairpin placed too high after a line break http://code.google.com/p/lilypond/issues/detail?id=650#c3 Patchy the autobot says: LGTM. Patch is identical to that for issue 1097. Please mark as duplicate if

Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC

2012-02-05 Thread lilypond
Comment #3 on issue 2271 by chh...@gmail.com: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 Well, also 0.6 works on PPC, just not on MacOSX 10.4. But using 0.4 for PPC and 0.6 for x86 is the pragmatic way to go. This should no increase the maint

Re: Issue 1097 in lilypond: better skylines for volta brackets

2012-02-05 Thread lilypond
Updates: Labels: Patch-review Comment #10 on issue 1097 by d...@gnu.org: better skylines for volta brackets http://code.google.com/p/lilypond/issues/detail?id=1097#c10 Patchy the autobot says: LGTM. Spacing changes look intentional in break-alignment-anchor-alignment, tablature-tie

Re: Issue 2269 in lilypond: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef

2012-02-05 Thread lilypond
Updates: Labels: Patch-review Comment #3 on issue 2269 by d...@gnu.org: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef http://code.google.com/p/lilypond/issues/detail?id=2269#c3 Patchy the autobot says: LGTM. ___ b

Re: Issue 2272 in lilypond: Long monosyllabic words collide with barlines

2012-02-05 Thread lilypond
Updates: Status: Accepted Comment #1 on issue 2272 by philehol...@gmail.com: Long monosyllabic words collide with barlines http://code.google.com/p/lilypond/issues/detail?id=2272 (No comment was entered for this change.) ___ bug-lilypond m

Re: Issue 2269 in lilypond: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef

2012-02-05 Thread lilypond
Comment #2 on issue 2269 by d...@gnu.org: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef http://code.google.com/p/lilypond/issues/detail?id=2269#c2 Issue 2269: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef http://codereview.appspot.com/56

Re: Issue 2269 in lilypond: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef

2012-02-05 Thread lilypond
Updates: Labels: Patch-new Comment #1 on issue 2269 by d...@gnu.org: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef http://code.google.com/p/lilypond/issues/detail?id=2269#c1 Issue 2269: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef

Re: Issue 2280 in lilypond: Patch: Directs lilypond option help to stderr

2012-02-05 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review Fixed_2_15_29 Comment #6 on issue 2280 by philehol...@gmail.com: Patch: Directs lilypond option help to stderr http://code.google.com/p/lilypond/issues/detail?id=2280 Pushed to staging as d5191631fada6a8cb71f5deb2d614d02e0196fdd _

Re: Issue 2282 in lilypond: Patch: Directs regtest output for last 2 files to stderr

2012-02-05 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review Fixed_2_15_29 Comment #3 on issue 2282 by philehol...@gmail.com: Patch: Directs regtest output for last 2 files to stderr http://code.google.com/p/lilypond/issues/detail?id=2282 Pushed to staging as 6f058d910b1db70c7adf9cf4394c7c3aa

Re: Issue 2281 in lilypond: Patch: Directs output from identifier-foll*.ly to stderr

2012-02-05 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review Fixed_2_15_29 Comment #2 on issue 2281 by philehol...@gmail.com: Patch: Directs output from identifier-foll*.ly to stderr http://code.google.com/p/lilypond/issues/detail?id=2281 Patch pushed to staging as eb472840de8a97a13dc3c2e5bd1

Re: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef

2012-02-05 Thread Phil Holmes
"Ole V. Villumsen" wrote in message news:loom.20120131t13151...@post.gmane.org... I'm not top posting. Cues are often used at or near the beginning of a piece. Furthermore, a cue is frequently in a different clef, so the \cueDuringWithClef command is handy. However, using this command at th

Issue 2285 in lilypond: Excessive processing time with systems-per-page

2012-02-05 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect New issue 2285 by philehol...@gmail.com: Excessive processing time with systems-per-page http://code.google.com/p/lilypond/issues/detail?id=2285 In the example below, processing time tends to infinite unless systems-per-page is set to 4. \v

Re: exceeding processing time when processing multiple scores withinonebook

2012-02-05 Thread Phil Holmes
"Martin Straeten" wrote in message news:f2bf03b2-c2c0-4583-9a6d-06bcc2c12...@gmail.com... for single staff-systems: systems-per-page 1,2 --> ok; 3 --> fails; 4 --> ok; 5 -->fails for double staff systems ( { << {\music} {\music} >> } instead of { \music }) processing fails for any value >1

Re: Issue 2268 in lilypond: Patch: Gets left Beam bounds correct with tempo indications

2012-02-05 Thread lilypond
Updates: Status: Duplicate Mergedinto: 2260 Comment #5 on issue 2268 by mts...@gmail.com: Patch: Gets left Beam bounds correct with tempo indications http://code.google.com/p/lilypond/issues/detail?id=2268 (No comment was entered for this change.) ___

Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time

2012-02-05 Thread lilypond
Comment #27 on issue 2260 by mts...@gmail.com: line-broken spanners start too far to the right, with \tempo and \time http://code.google.com/p/lilypond/issues/detail?id=2260 Issue 2268 has been merged into this issue. ___ bug-lilypond mailing list

Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time

2012-02-05 Thread lilypond
Comment #26 on issue 2260 by mts...@gmail.com: line-broken spanners start too far to the right, with \tempo and \time http://code.google.com/p/lilypond/issues/detail?id=2260 Issue 2267 has been merged into this issue. ___ bug-lilypond mailing list

Re: Issue 2267 in lilypond: Patch: Gets left Hairpin bounds correct with tempo indications

2012-02-05 Thread lilypond
Updates: Status: Duplicate Mergedinto: 2260 Comment #4 on issue 2267 by mts...@gmail.com: Patch: Gets left Hairpin bounds correct with tempo indications http://code.google.com/p/lilypond/issues/detail?id=2267 (No comment was entered for this change.)

Re: Issue 650 in lilypond: Broken hairpin placed too high after a line break

2012-02-05 Thread lilypond
Updates: Labels: Patch-new Comment #2 on issue 650 by mts...@gmail.com: Broken hairpin placed too high after a line break http://code.google.com/p/lilypond/issues/detail?id=650 Gets vertical skylines from grob stencils http://codereview.appspot.com/5626052 _

Re: Issue 1097 in lilypond: better skylines for volta brackets

2012-02-05 Thread lilypond
Comment #9 on issue 1097 by mts...@gmail.com: better skylines for volta brackets http://code.google.com/p/lilypond/issues/detail?id=1097#c9 Gets vertical skylines from grob stencils http://codereview.appspot.com/5626052 ___ bug-lilypond mailing l

Re: Issue 1097 in lilypond: better skylines for volta brackets

2012-02-05 Thread lilypond
Updates: Labels: Patch-new Comment #8 on issue 1097 by mts...@gmail.com: better skylines for volta brackets http://code.google.com/p/lilypond/issues/detail?id=1097#c8 Gets vertical skylines from grob stencils http://codereview.appspot.com/5626052 ___

Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord

2012-02-05 Thread lilypond
Updates: Status: Verified Comment #14 on issue 2229 by d...@gnu.org: Patch: Broadcast articulations not in EventChord http://code.google.com/p/lilypond/issues/detail?id=2229 Marking as verified since about half of LilyPond serves as a regtest for this and the specified commit is in

Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat

2012-02-05 Thread lilypond
Updates: Status: Verified Comment #15 on issue 2228 by elu...@gmail.com: Some users prefer to minimize partial beams rather than beam by the beat http://code.google.com/p/lilypond/issues/detail?id=2228 (No comment was entered for this change.) ___

Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes

2012-02-05 Thread lilypond
Comment #13 on issue 2256 by d...@gnu.org: empty strings: tabStaff insists on stringnumbers and looses notes http://code.google.com/p/lilypond/issues/detail?id=2256 Just making sure that this did not point to an overlooked issue. Thanks for the corroboration (corroperation?). __

Re: Issue 22 in lilypond: collision tuplet number and staff with increased spacing

2012-02-05 Thread lilypond
Comment #8 on issue 22 by gra...@percival-music.ca: collision tuplet number and staff with increased spacing http://code.google.com/p/lilypond/issues/detail?id=22 Still looks like it collides with #0.9 ___ bug-lilypond mailing list bug-lilypond@gn

Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes

2012-02-05 Thread lilypond
Comment #12 on issue 2256 by elu...@gmail.com: empty strings: tabStaff insists on stringnumbers and looses notes http://code.google.com/p/lilypond/issues/detail?id=2256 that wasn't criticism, just a statement! "Conversion to the new syntax should have worked with convert-ly -ed without man