Re: Feature request: multiplication should work on notes, chords and all rests

Pavel Roskin writes: > Quoting Xavier Scheuer : > >> On 15 December 2011 22:58, Pavel Roskin wrote: >>> Hello! >>> >>> For some reason, multiplication only works on full-measure rests >>> and silent rests. >>> >>> It would be nice to make it work on notes, chords and all kinds of >>> rests. For

Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system

Updates: Labels: -Patch-needs_work Patch-review Comment #8 on issue 2102 by k-ohara5...@oco.net: vertical spacing of a nonstaff line below the system http://code.google.com/p/lilypond/issues/detail?id=2102 Pavel pointed out that if this issue is Invalid, then the documentation is mi

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

Updates: Labels: -Patch-review Patch-countdown Comment #8 on issue 2100 by colinpkc...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100 (No comment was entered for this change.) __

Re: Issue 2107 in lilypond: new patch for lilypond-book on windows

Updates: Labels: -Patch-review Patch-countdown Comment #3 on issue 2107 by colinpkc...@gmail.com: new patch for lilypond-book on windows http://code.google.com/p/lilypond/issues/detail?id=2107 (No comment was entered for this change.) ___

Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo

Comment #3 on issue 2106 by colinpkc...@gmail.com: Patch: Build fixes for translated manuals: dependencies and a typo http://code.google.com/p/lilypond/issues/detail?id=2106 As this was pushed with 9ac7a5aaff66f2bd19184c9a23bccd195323e193, it should be marked fixed and the relarewd Rietveld

Re: Feature request: multiplication should work on notes, chords and all rests

Pavel Roskin gnu.org> writes: > For some reason, multiplication only works on full-measure rests > and silent rests. It works for notes, too, by scaling their duration without changing the way they are printed. We sometimes need to do that, most often to write triplets when it is not approp

Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system

Updates: Labels: -Patch-countdown Patch-needs_work Comment #7 on issue 2102 by colinpkc...@gmail.com: vertical spacing of a nonstaff line below the system http://code.google.com/p/lilypond/issues/detail?id=2102 Thanks for a quick reply, Keith! ___

Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system

Comment #6 on issue 2102 by k-ohara5...@oco.net: vertical spacing of a nonstaff line below the system http://code.google.com/p/lilypond/issues/detail?id=2102 Learning Manual A.2.4 is "Piano centered dynamics" and also

Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system

Comment #5 on issue 2102 by colinpkc...@gmail.com: vertical spacing of a nonstaff line below the system http://code.google.com/p/lilypond/issues/detail?id=2102 @plroskin: Would you reply with a tiny example, and the specific reference to "Piano centered dynamics", please? We'll need that i

Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight

Updates: Labels: -Patch-countdown Patch-push Comment #12 on issue 1377 by colinpkc...@gmail.com: Enhancement: make the last-page spacing more consistent and less tight http://code.google.com/p/lilypond/issues/detail?id=1377 Counted down to 20111215

Re: Issue 2057 in lilypond: Hairpin hits barline at line break

Updates: Labels: -Patch-countdown Patch-push Comment #50 on issue 2057 by colinpkc...@gmail.com: Hairpin hits barline at line break http://code.google.com/p/lilypond/issues/detail?id=2057 Counted down to 20111215 ___ bug-lilypond mailing

Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars

Updates: Labels: -Patch-countdown Patch-push Comment #8 on issue 2065 by colinpkc...@gmail.com: Scripts in cross-staff constructions can collide with span bars http://code.google.com/p/lilypond/issues/detail?id=2065 Counted down to 20111215

Re: Issue 2101 in lilypond: Doc: NR Added glissando grob skip snippet to 1.3.3

Updates: Labels: -Patch-countdown Patch-push Comment #3 on issue 2101 by colinpkc...@gmail.com: Doc: NR Added glissando grob skip snippet to 1.3.3 http://code.google.com/p/lilypond/issues/detail?id=2101 Counted down to 20111215 ___ bug

Re: Feature request: multiplication should work on notes, chords and all rests

Quoting Xavier Scheuer : On 15 December 2011 22:58, Pavel Roskin wrote: Hello! For some reason, multiplication only works on full-measure rests and silent rests. It would be nice to make it work on notes, chords and all kinds of rests. For short repetitions, \repeat unfold is an overkill, w

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

Updates: Status: Verified Comment #10 on issue 1798 by colingh...@gmail.com: Full measure rests take too little horizontal space compared to notes http://code.google.com/p/lilypond/issues/detail?id=1798 Verified with 2.15.23. Also confirmed old behaviour with 2.14.2. Attachments:

Re: Issue 2110 in lilypond: Improved example showing use of whiteout and layer properties for ties avoiding collision with staff objects

Comment #1 on issue 2110 by colingh...@gmail.com: Improved example showing use of whiteout and layer properties for ties avoiding collision with staff objects http://code.google.com/p/lilypond/issues/detail?id=2110 I'll prepare a patch for this. Once I've researched how to do so I'll upda

Issue 2110 in lilypond: Improved example showing use of whiteout and layer properties for ties avoiding collision with staff objects

Status: Accepted Owner: Labels: Type-Documentation New issue 2110 by colingh...@gmail.com: Improved example showing use of whiteout and layer properties for ties avoiding collision with staff objects http://code.google.com/p/lilypond/issues/detail?id=2110 The example added to the docume

Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with )

Updates: Status: Verified Comment #14 on issue 2076 by colingh...@gmail.com: Doc: improve NR 1.6.3 Instrument names (better to use \with ) http://code.google.com/p/lilypond/issues/detail?id=2076 Verified present in staging. ___ bug-lilypon

Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved.

Comment #7 on issue 2104 by julien.r...@gmail.com: Patch: Fix .dep file from lilypond-book when include paths are involved. http://code.google.com/p/lilypond/issues/detail?id=2104 I read "CG Section 9. Regression tests" but I can't figure this out: where do you get this diff from? OK, I se

Re: Feature request: multiplication should work on notes, chords and all rests

On 15 December 2011 22:58, Pavel Roskin wrote: > Hello! > > For some reason, multiplication only works on full-measure rests > and silent rests. > > It would be nice to make it work on notes, chords and all kinds of > rests. For short repetitions, \repeat unfold is an overkill, which > doesn't ma

Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages.

Updates: Labels: Patch-review Comment #7 on issue 2103 by lilypond...@gmail.com: Patch: Output a newline by default at the end of progress messages. http://code.google.com/p/lilypond/issues/detail?id=2103#c7 Patchy the autobot says: LGTM.

Feature request: multiplication should work on notes, chords and all rests

Hello! For some reason, multiplication only works on full-measure rests and silent rests. It would be nice to make it work on notes, chords and all kinds of rests. For short repetitions, \repeat unfold is an overkill, which doesn't make the source shorter: vs. \repeat unfold 2 { } vs. *2 He

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

Comment #32 on issue 460 by gra...@percival-music.ca: bar numbers for broken bars http://code.google.com/p/lilypond/issues/detail?id=460 hmm, there isn't even a regtest for this feature! Mike, could you add one? ___ bug-lilypond mailing list bug-

Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages.

Updates: Labels: -Patch-needs_work Patch-new Comment #6 on issue 2103 by gra...@percival-music.ca: Patch: Output a newline by default at the end of progress messages. http://code.google.com/p/lilypond/issues/detail?id=2103 could be. Let's trigger another test. _

Re: Issue 2098 in lilypond: Patch: Now use astyle 2.02.1

Updates: Labels: -Patch-countdown Patch-waiting Comment #4 on issue 2098 by gra...@percival-music.ca: Patch: Now use astyle 2.02.1 http://code.google.com/p/lilypond/issues/detail?id=2098 oops, sorry. I didn't mean this to go on a countdown, pending a policy discussion, but I forgot

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Updates: Labels: Patch-needs_work Comment #1 on issue 2109 by lilypond...@gmail.com: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109#c1 Patchy the autobot says: patch does not apply to current master _

Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions.

Updates: Labels: Patch-review Comment #1 on issue 2108 by lilypond...@gmail.com: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions. http://code.google.com/p/lilypond/issues/detail?id=2108#c1 Patchy the autobot says: LGTM. ___

Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Status: Accepted Owner: Labels: Type-Enhancement Patch-new New issue 2109 by gra...@percival-music.ca: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 asdf http://codereview.appspot.com/5434061/

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages

Comment #4 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to "programming error" messages http://code.google.com/p/lilypond/issues/detail?id=2085 I will try to get the simple fix done on Saturday. ___ bug-lilypon

Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions.

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2108 by mts...@gmail.com: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions. http://code.google.com/p/lilypond/issues/detail?id=2108 Implements avoidance of cross-staff-stem vs. articulation collisi

Re: Issue 2013 in lilypond: clang error flower/file-name.cc

Updates: Status: Verified Comment #14 on issue 2013 by gra...@percival-music.ca: clang error flower/file-name.cc http://code.google.com/p/lilypond/issues/detail?id=2013 (No comment was entered for this change.) ___ bug-lilypond mailing lis

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages

Comment #3 on issue 2085 by d...@gnu.org: Overriding stencil of StringNumber leads to "programming error" messages http://code.google.com/p/lilypond/issues/detail?id=2085 Since not being able to override the stencils to ##f (the obvious way to switch off string numbers) without warning lead

Re: Issue 2013 in lilypond: clang error flower/file-name.cc

Updates: Status: Fixed Labels: fixed_2_15_22 Comment #13 on issue 2013 by gra...@percival-music.ca: clang error flower/file-name.cc http://code.google.com/p/lilypond/issues/detail?id=2013 fixed b062d7bfeaa7baab1e2543417d41898ca5281c79

Re: Issue 2012 in lilypond: clang warning flower/file-cookie.cc

Updates: Status: Verified Comment #3 on issue 2012 by gra...@percival-music.ca: clang warning flower/file-cookie.cc http://code.google.com/p/lilypond/issues/detail?id=2012 (No comment was entered for this change.) ___ bug-lilypond mailing

Re: Issue 2012 in lilypond: clang warning flower/file-cookie.cc

Updates: Status: Fixed Labels: fixed_2_15_22 Comment #2 on issue 2012 by gra...@percival-music.ca: clang warning flower/file-cookie.cc http://code.google.com/p/lilypond/issues/detail?id=2012 fixed in either Reinhold's patch or my clang work. _

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

Updates: Labels: Patch-review Comment #7 on issue 2100 by lilypond...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100#c7 Patchy the autobot says: LGTM. turns out the problem was in the checking script, not the

Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects

Updates: Status: Verified Comment #19 on issue 409 by colingh...@gmail.com: Using whiteout and layer properties for ties avoiding collision with staff objects http://code.google.com/p/lilypond/issues/detail?id=409 OK, I'll mark this as verified and raise a new issue to fix the example

Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved.

Comment #6 on issue 2104 by julien.r...@gmail.com: Patch: Fix .dep file from lilypond-book when include paths are involved. http://code.google.com/p/lilypond/issues/detail?id=2104 I read "CG Section 9. Regression tests" but I can't figure this out: where do you get this diff from? The "Re

Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects

Comment #18 on issue 409 by pkx1...@gmail.com: Using whiteout and layer properties for ties avoiding collision with staff objects http://code.google.com/p/lilypond/issues/detail?id=409 The patch has been pushed so there is nothing that 'needs-work' anymore in that sense. I suggest if you

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

Updates: Labels: Patch-new Comment #6 on issue 2100 by lilypond...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100#c6 CG: explanation of branches for the impatient http://codereview.appspot.com/5484043

Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved.

Comment #5 on issue 2104 by gra...@percival-music.ca: Patch: Fix .dep file from lilypond-book when include paths are involved. http://code.google.com/p/lilypond/issues/detail?id=2104 I see tons of output in the regtest comparison like this: @@ -1,14 +1,14 @@ Parsing... -Renaming input to:

Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved.

Updates: Labels: Patch-needs_work Comment #4 on issue 2104 by lilypond...@gmail.com: Patch: Fix .dep file from lilypond-book when include paths are involved. http://code.google.com/p/lilypond/issues/detail?id=2104#c4 Patchy the autobot says: _

Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins

Updates: Labels: Patch-review Comment #9 on issue 1216 by lilypond...@gmail.com: DynamicTextSpanners should end like hairpins http://code.google.com/p/lilypond/issues/detail?id=1216#c9 Patchy the autobot says: LGTM. ___ bug-lilypond mailin

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

Updates: Status: Fixed Comment #9 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 Pushed to staging as fcfeacd25974cdc37bf9eb65d72902e56511b282. _