Re: Default placement of string number indication does not avoid sloping beam

2010-09-06 Thread Dmytro O. Redchuk
On Tue 31 Aug 2010, 17:39 Nick Payne wrote: \version 2.13.31 \relative c'' { a'16[ e c a e cis\5 a] } Nick Thank you, added as 1250: http://code.google.com/p/lilypond/issues/detail?id=1250 -- Dmytro O. Redchuk Bug Squad ___

Re: Issue 1242 in lilypond: Regtest resgression - page-spacing-tall-headfoot.ly

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1242 by brownian.box: Regtest resgression - page-spacing-tall-headfoot.ly http://code.google.com/p/lilypond/issues/detail?id=1242 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 1250 in lilypond: Default placement of string number indication does not avoid sloping beam

2010-09-06 Thread lilypond
Comment #1 on issue 1250 by brownian.box: Default placement of string number indication does not avoid sloping beam http://code.google.com/p/lilypond/issues/detail?id=1250 There is a workaround, posted by Xavier Scheuer: http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00560.html

Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #30 on issue 684 by brownian.box: Enhancement: MetronomeMark should support break-align-symbols http://code.google.com/p/lilypond/issues/detail?id=684 Thank all of you! ___ bug-lilypond mailing list

Issue 1250 in lilypond: Default placement of string number indication does not avoid sloping beam

2010-09-06 Thread lilypond
Status: Accepted Owner: Labels: Type-Collision Priority-Medium New issue 1250 by brownian.box: Default placement of string number indication does not avoid sloping beam http://code.google.com/p/lilypond/issues/detail?id=1250 Reported by Nick Payne:

Re: (de)crescendo on items with specified volume

2010-09-06 Thread Dmytro O. Redchuk
On Wed 01 Sep 2010, 23:29 Graham Percival wrote: On Wed, Sep 01, 2010 at 11:24:55PM +0100, Neil Puttock wrote: On 1 September 2010 22:51, Graham Percival gra...@percival-music.ca wrote: This looks like a harmless warning; I remember seeing it in 2003 or 2004 or something like that.  I

Re: segmentation fault with 2.13.32

2010-09-06 Thread Dmytro O. Redchuk
On Sat 04 Sep 2010, 16:22 Paul Scott wrote: I have reduced the problem to the presence of a \tempo command: \version 2.13.32 \score{ \new StaffGroup \new Staff { %The following line causes a segmentation fault \tempo \markup\bold{ Andante }

Re: 2.13.32 not honouring margins and staves going off page

2010-09-06 Thread Dmytro O. Redchuk
On Sun 05 Sep 2010, 21:46 Nick Payne wrote: There's still a problem with vertical spacing in that with no bottom-system-spacing command in the paper block, the lowest stave on some pages overlays the page number at the bottom of the page. I had to add bottom-system-spacing = #'((space .

Re: Issue 1246 in lilypond: Ledger lines overhanging end of stave

2010-09-06 Thread lilypond
Comment #1 on issue 1246 by Carl.D.Sorensen: Ledger lines overhanging end of stave http://code.google.com/p/lilypond/issues/detail?id=1246 This is the same as issue 1229. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1246 in lilypond: Ledger lines overhanging end of stave

2010-09-06 Thread lilypond
Updates: Status: Duplicate Mergedinto: 1229 Comment #2 on issue 1246 by Carl.D.Sorensen: Ledger lines overhanging end of stave http://code.google.com/p/lilypond/issues/detail?id=1246 Sorry, I didn't see the Duplicate status button earlier.

Re: Issue 1229 in lilypond: Notes may be placed above clef and key signature.

2010-09-06 Thread lilypond
Comment #5 on issue 1229 by Carl.D.Sorensen: Notes may be placed above clef and key signature. http://code.google.com/p/lilypond/issues/detail?id=1229 Issue 1246 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1229 in lilypond: Notes on ledger lines with stems pointed away from the staff overlap clef and staff ends in tight layouts

2010-09-06 Thread lilypond
Updates: Summary: Notes on ledger lines with stems pointed away from the staff overlap clef and staff ends in tight layouts Comment #6 on issue 1229 by Carl.D.Sorensen: Notes on ledger lines with stems pointed away from the staff overlap clef and staff ends in tight layouts

Re: Issue 1250 in lilypond: Default placement of string number indication does not avoid sloping beam

2010-09-06 Thread lilypond
Comment #2 on issue 1250 by Carl.D.Sorensen: Default placement of string number indication does not avoid sloping beam http://code.google.com/p/lilypond/issues/detail?id=1250 Is there a reason *not* to have #'add-stem-support = ##t be the default?

Re: Issue 1212 in lilypond: [PATCH] Add scheme binding for chain_callback (issue1890044)

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1212 by percival.music.ca: [PATCH] Add scheme binding for chain_callback (issue1890044) http://code.google.com/p/lilypond/issues/detail?id=1212 (No comment was entered for this change.) ___

Re: Issue 1124 in lilypond: implement \eyeglasses using a 'path expression

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #5 on issue 1124 by percival.music.ca: implement \eyeglasses using a 'path expression http://code.google.com/p/lilypond/issues/detail?id=1124 To verify this issue, I clicked on the link that Patrick provided, to check that the patch actually was

Re: Issue 1212 in lilypond: [PATCH] Add scheme binding for chain_callback (issue1890044)

2010-09-06 Thread lilypond
Comment #3 on issue 1212 by percival.music.ca: [PATCH] Add scheme binding for chain_callback (issue1890044) http://code.google.com/p/lilypond/issues/detail?id=1212 To verify this, I went to our web git interface: http://git.savannah.gnu.org/gitweb/?p=lilypond.git and typed in chain_callback

Re: Issue 1185 in lilypond: version numbers for large new features

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #3 on issue 1185 by percival.music.ca: version numbers for large new features http://code.google.com/p/lilypond/issues/detail?id=1185 (No comment was entered for this change.) ___ bug-lilypond mailing

Re: 2.13.32 not honouring margins and staves going off page

2010-09-06 Thread Nick Payne
On 05/09/10 21:46, Nick Payne wrote: On 05/09/10 09:33, Neil Puttock wrote: On 5 September 2010 00:07, Nick Paynenick.pa...@internode.on.net wrote: I haven't been able to reproduce this behaviour with a small example, but I'm getting some staves in a score where lilypond tries to fit too

Issue 1252 in lilypond: Music overflows page (one staff per system, default spacing settings, some marks)

2010-09-06 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Medium New issue 1252 by brownian.box: Music overflows page (one staff per system, default spacing settings, some marks) http://code.google.com/p/lilypond/issues/detail?id=1252 Reported by Nick Payne:

Re: 2.13.32 not honouring margins and staves going off page

2010-09-06 Thread Dmytro O. Redchuk
On Mon 06 Sep 2010, 22:09 Nick Payne wrote: this short example shows the problem with staves going off the bottom of the page: %= \version 2.13.32 %#(set-global-staff-size 24.5) \relative c'' { \time 12/8 \repeat unfold 64 { \repeat unfold 3 {

(no subject)

2010-09-06 Thread Bryan Previte
http://codacup.tripod.com/ ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 389 in lilypond: \t - tab in LSR snippets

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #6 on issue 389 by percival.music.ca: \t - tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Since nobody has mentioned any \t chars again, I'll make this verified. ___ bug-lilypond

Re: Issue 1201 in lilypond: fix for 1112 produces bad page breaking in make test and doc

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #18 on issue 1201 by percival.music.ca: fix for 1112 produces bad page breaking in make test and doc http://code.google.com/p/lilypond/issues/detail?id=1201 I just looked at at the official pdf for regtests for 2.13.32, and saw that bookparts.ly

Re: Issue 1248 in lilypond: 2.13.32 automatic-polyphony-drumstaff.ly: unbound open-file

2010-09-06 Thread lilypond
Updates: Summary: 2.13.32 automatic-polyphony-drumstaff.ly: unbound open-file Comment #1 on issue 1248 by percival.music.ca: 2.13.32 automatic-polyphony-drumstaff.ly: unbound open-file http://code.google.com/p/lilypond/issues/detail?id=1248 More explanatory name.

Re: Issue 1243 in lilypond: Regtest resgression - tie-direction-manual.ly

2010-09-06 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1243 by percival.music.ca: Regtest resgression - tie-direction-manual.ly http://code.google.com/p/lilypond/issues/detail?id=1243 Correction: those open-file messages were added in .31, but removed in .32. The final result is that this

Re: Issue 1197 in lilypond: Doc: Update NR for new \tempo syntax

2010-09-06 Thread lilypond
Comment #5 on issue 1197 by pkx1...@hotmail.com: Doc: Update NR for new \tempo syntax http://code.google.com/p/lilypond/issues/detail?id=1197 Patch pushed - commit: 6c1ce19cc7e315a892416a004b9c3b22694dae50. LSR/Snippet tags still to be modified. The three snippets that are explicitly

Re: Issue 1124 in lilypond: implement \eyeglasses using a 'pathexpression

2010-09-06 Thread Phil Holmes
lilyp...@googlecode.com wrote in message news:5-9567054385019064696-277111724243982225-lilypond=googlecode@googlecode.com... Updates: Status: Verified Comment #5 on issue 1124 by percival.music.ca: implement \eyeglasses using a 'path expression

Re: Issue 1124 in lilypond: implement \eyeglasses using a 'pathexpression

2010-09-06 Thread Graham Percival
On Mon, Sep 6, 2010 at 3:59 PM, Phil Holmes m...@philholmes.net wrote: lilyp...@googlecode.com wrote in message news:5-9567054385019064696-277111724243982225-lilypond=googlecode@googlecode.com... Comment #5 on issue 1124 by percival.music.ca: implement \eyeglasses using a 'path expression

Re: (de)crescendo on items with specified volume

2010-09-06 Thread Mark Polesky
Dmytro O. Redchuk wrote: I am very sorry, i can not find original post; anyway. Original poster, please, provide a minimal example. I've tried[1] those lines by Mark[2] with no success -- i could not reproduce error message mentioned. I am sorry, very probably this is my fault. Please,

Re: Issue 1239 in lilypond: [PATCH] Make pure-print-callbacks public (issue1983047)

2010-09-06 Thread lilypond
Updates: Labels: Priority-Postponed Comment #2 on issue 1239 by Carl.D.Sorensen: [PATCH] Make pure-print-callbacks public (issue1983047) http://code.google.com/p/lilypond/issues/detail?id=1239 Although the patch works, the idea seems to be not yet ready for inclusion in the code

Issue 1253 in lilypond: programming error: (de)crescendo on items with specified volume.

2010-09-06 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Medium Warning New issue 1253 by brownian.box: programming error: (de)crescendo on items with specified volume. http://code.google.com/p/lilypond/issues/detail?id=1253

Re: (de)crescendo on items with specified volume

2010-09-06 Thread Dmytro O. Redchuk
On Mon 06 Sep 2010, 08:47 Mark Polesky wrote: Dmytro, Since the error is with the midi engine, you need to add a \midi block to the \score (see below). :-) Thanks! Thanks to all of you, added as 1253: http://code.google.com/p/lilypond/issues/detail?id=1253 -- Dmytro O. Redchuk Bug

Re: Issue 1124 in lilypond: implement \eyeglasses using a'pathexpression

2010-09-06 Thread Phil Holmes
Graham Percival gra...@percival-music.ca wrote in message news:aanlktiks6pdt9yzbocgcmhtxpsrkazpzo3n09tmfi...@mail.gmail.com... On Mon, Sep 6, 2010 at 3:59 PM, Phil Holmes m...@philholmes.net wrote: I don't understand why it took 22 days to check that link. FWIW I don't think it can be

Re: Issue 1197 in lilypond: Doc: Update NR for new \tempo syntax

2010-09-06 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_33 Comment #6 on issue 1197 by PhilEHolmes: Doc: Update NR for new \tempo syntax http://code.google.com/p/lilypond/issues/detail?id=1197 I've changed the LSR to show these as Staff tags.

Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication causes segfault

2010-09-06 Thread Paul Scott
On Mon, Sep 06, 2010 at 10:57:36AM -0700, Paul Scott wrote: On Mon, Sep 06, 2010 at 08:32:24AM +, lilyp...@googlecode.com wrote: Status: Accepted Owner: Labels: Type-Defect Priority-Critical Regression New issue 1251 by brownian.box: StaffGroup with pauses and tempo

Re: Issue 1124 in lilypond: implement \eyeglasses using a'pathexpression

2010-09-06 Thread Patrick McCarty
On Mon, Sep 6, 2010 at 11:03 AM, Phil Holmes m...@philholmes.net wrote: Graham Percival gra...@percival-music.ca wrote: On Mon, Sep 6, 2010 at 3:59 PM, Phil Holmes m...@philholmes.net wrote: FWIW I don't think it can be verified in Windows, since I don't seem able to write SVG files. Oh

Re: Issue 687 in lilypond: Enhancement: inequal MIDI quantization of equal durations (swing, rubato)

2010-09-06 Thread lilypond
Comment #17 on issue 687 by chicagogrooves: Enhancement: inequal MIDI quantization of equal durations (swing, rubato) http://code.google.com/p/lilypond/issues/detail?id=687 Happy labor day - the swing.ly file is still not as parameterized as I'd liked, but I cleaned up its formatting, and

Re: Issue 687 in lilypond: Enhancement: inequal MIDI quantization of equal durations (swing, rubato)

2010-09-06 Thread lilypond
Comment #18 on issue 687 by chicagogrooves: Enhancement: inequal MIDI quantization of equal durations (swing, rubato) http://code.google.com/p/lilypond/issues/detail?id=687 Additionally: Here's an example of the calling code groove = { c4 c4 c8 c8 c8 c8 } \swingIt #'eighth {

Re: Issue 1197 in lilypond: Doc: Update NR for new \tempo syntax

2010-09-06 Thread lilypond
Updates: Status: Accepted Labels: -fixed_2_13_33 Comment #7 on issue 1197 by percival.music.ca: Doc: Update NR for new \tempo syntax http://code.google.com/p/lilypond/issues/detail?id=1197 Technically we need to wait until the next LSR-git update.

Re: Issue 1250 in lilypond: Default placement of string number indication does not avoid sloping beam

2010-09-06 Thread lilypond
Comment #3 on issue 1250 by n.puttock: Default placement of string number indication does not avoid sloping beam http://code.google.com/p/lilypond/issues/detail?id=1250 Probably not, especially since they're really too big to look good close to the notehead without either changing the font

Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication causes segfault

2010-09-06 Thread lilypond
Updates: Status: Fixed Owner: n.puttock Labels: fixed_2_13_33 Comment #1 on issue 1251 by n.puttock: StaffGroup with pauses and tempo indication causes segfault http://code.google.com/p/lilypond/issues/detail?id=1251 (No comment was entered for this change.)

Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication causes segfault

2010-09-06 Thread Paul Scott
On Mon, Sep 06, 2010 at 09:50:11PM +0100, Neil Puttock wrote: On 6 September 2010 20:03, Paul Scott waterho...@ultrasw.com wrote: Now I get mixed results with \tempo placement.  (bug 684)  Some start over the time signature and some start over the key signature.  One of those placed

Re: Issue 1232 in lilypond: Misplaced tremolo in tablatures

2010-09-06 Thread lilypond
Updates: Status: fixed Labels: fixed_2_13_32 Comment #1 on issue 1232 by n.puttock: Misplaced tremolo in tablatures http://code.google.com/p/lilypond/issues/detail?id=1232 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 1233 in lilypond: Tremolos in tablatures are too massive

2010-09-06 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_32 Comment #1 on issue 1233 by n.puttock: Tremolos in tablatures are too massive http://code.google.com/p/lilypond/issues/detail?id=1233 (No comment was entered for this change.) ___

Re: Issue 389 in lilypond: \t - tab in LSR snippets

2010-09-06 Thread lilypond
Comment #7 on issue 389 by n.puttock: \t - tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Since nobody has mentioned any \t chars again, I'll make this verified. I doubt anybody's mentioned it since (AFAICT) any characters which need escaping in snippets are

Re: Issue 687 in lilypond: Enhancement: inequal MIDI quantization of equal durations (swing, rubato)

2010-09-06 Thread Peter Chubb
lilypond == lilypond lilyp...@googlecode.com writes: lilypond Comment #18 on issue 687 by chicagogrooves: Enhancement: lilypond inequal MIDI quantization of equal durations (swing, rubato) lilypond http://code.google.com/p/lilypond/issues/detail?id=687 Thanks, but there're still issues: When