Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch

2011-12-09 Thread lilypond
Updates: Status: Fixed Labels: -Patch-new fixed_2_15_22 Comment #4 on issue 2068 by gra...@percival-music.ca: Patch: Doc: CG: add instructions for staging branch http://code.google.com/p/lilypond/issues/detail?id=2068 pushed b963dc41847ab077d0bf32e74d2e168ea2a84883 _

Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch

2011-12-09 Thread lilypond
Comment #3 on issue 2068 by lilypond...@gmail.com: Patch: Doc: CG: add instructions for staging branch http://code.google.com/p/lilypond/issues/detail?id=2068#c3 Doc: CG: add instructions for staging branch http://codereview.appspot.com/5467051 _

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

2011-12-09 Thread lilypond
Updates: Labels: Patch-review Comment #10 on issue 2075 by lilypond...@gmail.com: Implement GOP 9 - behavior of make doc http://code.google.com/p/lilypond/issues/detail?id=2075#c10 Patchy the autobot says: LGTM. ___ bug-lilypond mailing li

Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default.

2011-12-09 Thread lilypond
Updates: Labels: Patch-needs_work Comment #7 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap EventChord around rhythmic events by default. http://code.google.com/p/lilypond/issues/detail?id=2070#c7 Patchy the autobot says: balloon.log: not an articulation 8 ___

Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes

2011-12-09 Thread lilypond
Updates: Labels: Patch-needs_work Comment #4 on issue 1798 by lilypond...@gmail.com: Full measure rests take too little horizontal space compared to notes http://code.google.com/p/lilypond/issues/detail?id=1798#c4 Patchy the autobot says: multi-measure-rest.ly loses the very very very

Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes

2011-12-09 Thread lilypond
Updates: Labels: Patch-new Comment #3 on issue 1798 by mts...@gmail.com: Full measure rests take too little horizontal space compared to notes http://code.google.com/p/lilypond/issues/detail?id=1798#c3 Makes multi-measure-rest measures the correct length. http://codereview.appspot.co

Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning

2011-12-09 Thread lilypond
Comment #12 on issue 1228 by x.sche...@gmail.com: \override RestCollision #'positioning-done = #merge-rests-on-positioning http://code.google.com/p/lilypond/issues/detail?id=1228 It would be nice if someone could eventually implement this into LilyPond. Please see Thomas Morley's attached fi

Issue 1377 should be pushed now?

2011-12-09 Thread Xavier Scheuer
Hi Joe, dear developers, bug squad, Issue 1377 is tagged as "Patch-push" since more than one month now, should it be pushed, go under a countdown? http://code.google.com/p/lilypond/issues/detail?id=1377 As said David 2 weeks ago: "What's up with this one?". Thanks for your attention. Cheers, Xav

Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default.

2011-12-09 Thread lilypond
Updates: Labels: Patch-new Comment #6 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord around rhythmic events by default. http://code.google.com/p/lilypond/issues/detail?id=2070#c6 Don't wrap EventChord around rhythmic events by default. This changes quite a number of thin

Doc: alternativeNumberingStyle (fix issue 2059) should be documented

2011-12-09 Thread Xavier Scheuer
On 7 December 2011 23:44, Carl Sorensen wrote: > > This should become a new issue, type Documentation. > > Thanks, The use of this \set Score.alternativeNumberingStyle = #'number or \set Score.alternativeNumberingStyle = #'numbers-with-letters (from the fix of issue 2059 "Bar numbering of

Re: Set global staff size as command line option

2011-12-09 Thread Xavier Scheuer
On 9 December 2011 10:27, Colin Hall wrote: > > Added as issue 2090 > > http://code.google.com/p/lilypond/issues/detail?id=2090 This is nice to add this to the tracker. It would be nice to add my initial request (first message of this thread) to the tracker also. Maybe I was not clear, but that

Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows

2011-12-09 Thread Eluze
Am 09.12.2011, 10:23 Uhr, schrieb : Command line quoting is properly documented here with an example of quoting suitable for a UNIX shell: http://lilypond.org/doc/v2.14/Documentation/usage/command_002dline-usage It would be helpful for Windows users to have some guidance on proper quoting

Re: Issue 2088 in lilypond: pointer confusion with clang++

2011-12-09 Thread lilypond
Comment #2 on issue 2088 by russell@gmail.com: pointer confusion with clang++ http://code.google.com/p/lilypond/issues/detail?id=2088 At least the following changes are necessary if the lily-proto.hh is changed as suggested above. Again, I will test and examine further this weekend w

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

2011-12-09 Thread lilypond
Updates: Labels: Patch-new Comment #9 on issue 2075 by philehol...@gmail.com: Implement GOP 9 - behavior of make doc http://code.google.com/p/lilypond/issues/detail?id=2075#c9 Initial reduction of make doc op - Issue 2075 This proposed patch reduces output to 113,500 lines by pushing

Re: Issue 1964 in lilypond: lilydev 2.0

2011-12-09 Thread lilypond
Comment #6 on issue 1964 by d...@gnu.org: lilydev 2.0 http://code.google.com/p/lilypond/issues/detail?id=1964 With regard to the gcc problem, here is an update from the Ubuntu crowd. https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/897583> So it would appear that gcc-4.6 - 4.6.2-6ubuntu1 w

Re: Issue 2088 in lilypond: pointer confusion with clang++

2011-12-09 Thread lilypond
Comment #1 on issue 2088 by russell@gmail.com: pointer confusion with clang++ http://code.google.com/p/lilypond/issues/detail?id=2088 The existing code uses a G++ extension (described in GCC manual 7.6), which allows this conversion of member function pointer to straight function poin

Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch

2011-12-09 Thread lilypond
Updates: Labels: Patch-new Comment #2 on issue 2068 by gra...@percival-music.ca: Patch: Doc: CG: add instructions for staging branch http://code.google.com/p/lilypond/issues/detail?id=2068#c2 Doc: CG: add instructions for staging branch http://codereview.appspot.com/5467051 ___

Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond

2011-12-09 Thread lilypond
Comment #2 on issue 2072 by d...@gnu.org: Add proper complex variables to Lilypond http://code.google.com/p/lilypond/issues/detail?id=2072 After thinking about it, assignments are possible only in contexts where strings can't occur by themselves. So it should actually be possible to use t

Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing

2011-12-09 Thread lilypond
Updates: Status: Fixed Comment #9 on issue 2069 by mts...@gmail.com: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing http://code.google.com/p/lilypond/issues/detail?id=2069 Pushed with 975c00a63710da2472f57fbb6d5a484541f27c66. As the hairpin patch

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

2011-12-09 Thread lilypond
Status: Accepted Owner: carl.d.s...@gmail.com Labels: Type-Maintainability New 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 Strictly a change "under the hood": could lily-git.tcl put commits on its

Re: Fwd: bug or feature with the extent of NoteColumn with "2.15.20" ?

2011-12-09 Thread Colin Hall
On Fri, Dec 09, 2011 at 02:11:38AM -0800, Graham Percival wrote: > On Fri, Dec 09, 2011 at 10:06:53AM +, Colin Hall wrote: > > > It seems that in "2.15.20" the arpeggio is part of the NoteColumn. (But > > > not > > > the DotColumn or the AccidentalPlacement) > > > The IR 3.2.71 note-column-int

Issue 2091 in lilypond: bug or feature with the extent of NoteColumn with 2.15.20

2011-12-09 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect New issue 2091 by colingh...@gmail.com: bug or feature with the extent of NoteColumn with 2.15.20 http://code.google.com/p/lilypond/issues/detail?id=2091 Thomas Morley googlemail.com> sent an email http://article.gmane.org/gmane.comp.gnu.lil

Re: Issue 2089 in lilypond: dangerous redefinition of SCM s / Moment s

2011-12-09 Thread lilypond
Updates: Status: Verified Comment #3 on issue 2089 by colingh...@gmail.com: dangerous redefinition of SCM s / Moment s http://code.google.com/p/lilypond/issues/detail?id=2089 Verified that this commit is in the repo. ___ bug-lilypond maili

Re: Fwd: bug or feature with the extent of NoteColumn with "2.15.20" ?

2011-12-09 Thread Graham Percival
On Fri, Dec 09, 2011 at 10:06:53AM +, Colin Hall wrote: > > It seems that in "2.15.20" the arpeggio is part of the NoteColumn. (But not > > the DotColumn or the AccidentalPlacement) > > The IR 3.2.71 note-column-interface states only stems and noteheads. > > I'm unable to determine if this is

Fwd: bug or feature with the extent of NoteColumn with "2.15.20" ?

2011-12-09 Thread Colin Hall
On Thu, Dec 08, 2011 at 12:54:12AM +0100, Thomas Morley wrote: > > trying to compile a function manipulating the NoteColumn with "2.15.20" I > noticed some differences to "2.14.2" > So I wrote a test-function to display the grob-length: > > \version "2.14.2" > %\version "2.15.20" > > #(define (x-

Re: bug or feature with the extent of NoteColumn with "2.15.20" ?

2011-12-09 Thread Colin Hall
On Thu, Dec 08, 2011 at 12:54:12AM +0100, Thomas Morley wrote: > > trying to compile a function manipulating the NoteColumn with "2.15.20" I > noticed some differences to "2.14.2" > So I wrote a test-function to display the grob-length: > > \version "2.14.2" > %\version "2.15.20" > > #(define (x

Re: Set global staff size as command line option

2011-12-09 Thread Colin Hall
On Thu, Dec 08, 2011 at 11:32:07AM +, James wrote: > On 8 December 2011 10:50, Eluze wrote: > > > Windows has a crappy command line. Try using double quotes " instead of > >> the single quotes ' suggested above. > > > > thanks for the hint - it works now! > > > > maybe a hint in "Usage" who

Re: Issue 1964 in lilypond: lilydev 2.0

2011-12-09 Thread lilypond
Comment #5 on issue 1964 by pkx1...@gmail.com: lilydev 2.0 http://code.google.com/p/lilypond/issues/detail?id=1964 32 bit or 64 bit? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 2090 in lilypond: Add documentation for command line quoting on Windows

2011-12-09 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation New issue 2090 by colingh...@gmail.com: Add documentation for command line quoting on Windows http://code.google.com/p/lilypond/issues/detail?id=2090 Eluze reported unexpected behaviour when using command line options under Windows:

Re: Issue 2089 in lilypond: dangerous redefinition of SCM s / Moment s

2011-12-09 Thread lilypond
Updates: Status: Fixed Labels: Fixed_2_5_22 Comment #2 on issue 2089 by d...@gnu.org: dangerous redefinition of SCM s / Moment s http://code.google.com/p/lilypond/issues/detail?id=2089 c95a76f15bb0ab0960ed7783762611254cabbd91 to staging. _

Re: Issue 2036 in lilypond: make test in flower subdirectory produces lots of warnings with g++ 4.6

2011-12-09 Thread lilypond
Updates: Status: Verified Comment #6 on issue 2036 by colingh...@gmail.com: make test in flower subdirectory produces lots of warnings with g++ 4.6 http://code.google.com/p/lilypond/issues/detail?id=2036 I have verified this commit is in the repo. __

Re: Issue 2089 in lilypond: dangerous redefinition of SCM s / Moment s

2011-12-09 Thread lilypond
Updates: Status: Started Owner: d...@gnu.org Comment #1 on issue 2089 by d...@gnu.org: dangerous redefinition of SCM s / Moment s http://code.google.com/p/lilypond/issues/detail?id=2089 According to the view of the compiler, s is redefined in the same scope (dangerous) while

Re: Issue 1964 in lilypond: lilydev 2.0

2011-12-09 Thread lilypond
Comment #4 on issue 1964 by gra...@percival-music.ca: lilydev 2.0 http://code.google.com/p/lilypond/issues/detail?id=1964 handy link to the instructions: http://lilypond.org/doc/v2.15/Documentation/contributor/building-an-ubuntu-distro No need to wait for a newer lily-git.tcl, since that has no

Re: Issue 1964 in lilypond: lilydev 2.0

2011-12-09 Thread lilypond
Comment #3 on issue 1964 by d...@gnu.org: lilydev 2.0 http://code.google.com/p/lilypond/issues/detail?id=1964 Lilypond has a fix for the gcc-4.6 code generation bug. The rest of 11.10 appears mostly unaffected. It is conceivable that there are other code stability issues, but I have been u

Re: Issue 2077 in lilypond: Patch: Provide Scheme sandbox.

2011-12-09 Thread lilypond
Updates: Status: Fixed Labels: -Patch-push Fixed_2_5_22 Comment #5 on issue 2077 by d...@gnu.org: Patch: Provide Scheme sandbox. http://code.google.com/p/lilypond/issues/detail?id=2077 Pushed ae91f1e066925892308a1171df9399eeb0ecc77c to staging. This does not preclude merging p

Re: Issue 2087 in lilypond: Patch: Fixes various warnings from clang++

2011-12-09 Thread lilypond
Updates: Labels: Patch-review Comment #1 on issue 2087 by lilypond...@gmail.com: Patch: Fixes various warnings from clang++ http://code.google.com/p/lilypond/issues/detail?id=2087#c1 Patchy the autobot says: LGTM. no changes ___ bug-lilyp

Re: Issue 460 in lilypond: bar numbers for broken bars

2011-12-09 Thread lilypond
Updates: Labels: Patch-review Comment #24 on issue 460 by lilypond...@gmail.com: bar numbers for broken bars http://code.google.com/p/lilypond/issues/detail?id=460#c24 Patchy the autobot says: LGTM. no changes is good changes ___ bug-lily