Re: Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes

2011-07-14 Thread lilypond
Updates: Status: Verified Mergedinto: Comment #4 on issue 1759 by brownian.box: hairpin aligns to lyrics instead of notes http://code.google.com/p/lilypond/issues/detail?id=1759 (No comment was entered for this change.) ___

Re: Issue 1758 in lilypond: layout-set-staff-size doesn't work properly

2011-07-14 Thread lilypond
Updates: Status: Verified Mergedinto: Comment #3 on issue 1758 by brownian.box: layout-set-staff-size doesn't work properly http://code.google.com/p/lilypond/issues/detail?id=1758 (No comment was entered for this change.) ___

Re: Issue 1219 in lilypond: Broken tie may become a too small dot

2011-07-14 Thread lilypond
Updates: Status: Verified Mergedinto: Comment #10 on issue 1219 by brownian.box: Broken tie may become a too small dot http://code.google.com/p/lilypond/issues/detail?id=1219 (No comment was entered for this change.) ___

Re: Issue 840 in lilypond: broken ties too short when time signature changes

2011-07-14 Thread lilypond
Updates: Status: Verified Mergedinto: Comment #2 on issue 840 by brownian.box: broken ties too short when time signature changes http://code.google.com/p/lilypond/issues/detail?id=840 (No comment was entered for this change.) ___

Re: Issue 1748 in lilypond: Defect in glissando handling

2011-07-14 Thread lilypond
Updates: Status: Verified Comment #5 on issue 1748 by brownian.box: Defect in glissando handling http://code.google.com/p/lilypond/issues/detail?id=1748 Verified with 2.15.5. Shouldn't `backport' be removed? ___ bug-lilypond mailing list

Re: Issue 298 in lilypond: Ties do not appear when shortened because of an accidental

2011-07-14 Thread lilypond
Updates: Owner: --- Labels: -Priority-Low Priority-Medium Comment #6 on issue 298 by brownian.box: Ties do not appear when shortened because of an accidental http://code.google.com/p/lilypond/issues/detail?id=298 Issues 840 and 1219 have other good samples.

Re: Issue 1748 in lilypond: Defect in glissando handling

2011-07-14 Thread lilypond
Updates: Status: Fixed Comment #6 on issue 1748 by brownian.box: Defect in glissando handling http://code.google.com/p/lilypond/issues/detail?id=1748 Oops, sorry, I guess it should be backported yet. ___ bug-lilypond mailing list

Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura)

2011-07-14 Thread Dmytro O. Redchuk
On Wed 13 Jul 2011, 18:54 lilyp...@googlecode.com wrote: Comment #20 on issue 75 by carl.d.s...@gmail.com: Slurs cannot be nested (including acciaccatura and appoggiatura) http://code.google.com/p/lilypond/issues/detail?id=75 Scratch those commits. In order to make every commit build the

Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf

2011-07-14 Thread lilypond
Updates: Status: Verified Comment #7 on issue 1710 by brownian.box: rearrange flag definitions in feta-flags.mf http://code.google.com/p/lilypond/issues/detail?id=1710 (No comment was entered for this change.) ___ bug-lilypond mailing

Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax

2011-07-14 Thread lilypond
Comment #5 on issue 1110 by lemzw...@googlemail.com: Wrong octave of repetition chord with \relative and #{ #} syntax http://code.google.com/p/lilypond/issues/detail?id=1110 BTW, this is a regression (well, sort of, since it refers to a development version): `q' within #{ ... #} has worked

Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura)

2011-07-14 Thread Urs Liska
Would love to do, but 2.14.2 isn't out yet ... Am 14.07.2011 10:05, schrieb Dmytro O. Redchuk: Still waiting to verify this in 2.14.2 :-) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals

2011-07-14 Thread lilypond
Comment #10 on issue 1750 by lilyli...@googlemail.com: Documentation suggestion: transposition resulting in triple accidentals http://code.google.com/p/lilypond/issues/detail?id=1750 Verified for 2.15.5 Cannot mark as verified, as 2.14.2 isn't out yet

Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault

2011-07-14 Thread lilypond
Comment #9 on issue 1715 by lilyli...@googlemail.com: Ligature and ambitus cause segfault http://code.google.com/p/lilypond/issues/detail?id=1715 Compiles without problem on 2.15.5 2.14.2 isn't out yet to check ___ bug-lilypond mailing list

Issue 1761 in lilypond: cue notes clash with main voice

2011-07-14 Thread lilypond
Status: Accepted Owner: Labels: Type-Collision Priority-Medium New issue 1761 by lemzw...@googlemail.com: cue notes clash with main voice http://code.google.com/p/lilypond/issues/detail?id=1761 \version 2.15.2 \header { texidoc = Cue notes clash with the main voice if starting at the

2.14.2

2011-07-14 Thread Urs Liska
Hi guys, as you may have noticed I gained some activity again lately. I think I have to apologize that I faded out of my Bug Squad duty silently half a year ago. I don't apologize that I didn't have the necessary time anymore - as that's life and the character of open source projects. But I

Re: Issue 1762 in lilypond: mutual cues fail

2011-07-14 Thread lilypond
Comment #1 on issue 1762 by lemzw...@googlemail.com: mutual cues fail http://code.google.com/p/lilypond/issues/detail?id=1762 This has been tested with 2.15.4. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Issue 1762 in lilypond: mutual cues fail

2011-07-14 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Medium New issue 1762 by lemzw...@googlemail.com: mutual cues fail http://code.google.com/p/lilypond/issues/detail?id=1762 \version 2.15.2 \header { texidoc = Mutual inclusion of cues should work. Here is a counterexample: The notes

Issue 1763 in lilypond: OttavaBracket doesn't follow fontSize

2011-07-14 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Medium New issue 1763 by lemzw...@googlemail.com: OttavaBracket doesn't follow fontSize http://code.google.com/p/lilypond/issues/detail?id=1763 \version 2.15.4 \header { texidoc = The `8va' string should become smaller, as is the

Re: 2.14.2

2011-07-14 Thread Carl Sorensen
On 7/14/11 6:23 AM, Urs Liska lilyli...@googlemail.com wrote: Hi guys, as you may have noticed I gained some activity again lately. Glad to have you back! I think I have to apologize that I faded out of my Bug Squad duty silently half a year ago. Apology accepted. This as a general

Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals

2011-07-14 Thread lilypond
Updates: Labels: verified_2_15_5 Comment #11 on issue 1750 by lilyli...@googlemail.com: Documentation suggestion: transposition resulting in triple accidentals http://code.google.com/p/lilypond/issues/detail?id=1750 (No comment was entered for this change.)

Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault

2011-07-14 Thread lilypond
Updates: Labels: verified_2_15_5 Comment #10 on issue 1715 by lilyli...@googlemail.com: Ligature and ambitus cause segfault http://code.google.com/p/lilypond/issues/detail?id=1715 (No comment was entered for this change.) ___ bug-lilypond

Re: 2.14.2

2011-07-14 Thread Urs Liska
Am 14.07.2011 14:53, schrieb Carl Sorensen: On 7/14/11 6:23 AM, Urs Liskalilyli...@googlemail.com wrote: Hi guys, as you may have noticed I gained some activity again lately. Glad to have you back! I think I have to apologize that I faded out of my Bug Squad duty silently half a year ago.

Re: 2.14.2

2011-07-14 Thread Graham Percival
On Thu, Jul 14, 2011 at 06:53:45AM -0600, Carl Sorensen wrote: On 7/14/11 6:23 AM, Urs Liska lilyli...@googlemail.com wrote: ATM there are many issues to verify that are marked as fixed_2_14_2. So before this version is released the issues can't be verified. I think that in the past we

Re: Issue 1757 in lilypond: Footnotes cannot attach to many layout objects/grobs

2011-07-14 Thread lilypond
Updates: Labels: Priority-Low Comment #4 on issue 1757 by percival.music.ca: Footnotes cannot attach to many layout objects/grobs http://code.google.com/p/lilypond/issues/detail?id=1757 (No comment was entered for this change.) ___

Re: Issue 1721 in lilypond: Doc: translated docs should use @rlsrnamed instead of @rlsr

2011-07-14 Thread lilypond
Comment #2 on issue 1721 by pkx1...@gmail.com: Doc: translated docs should use @rlsrnamed instead of @rlsr http://code.google.com/p/lilypond/issues/detail?id=1721 hello, is this a find/replace thing or a programming thing? I can download the translation branch and do a find/replace and then

Re: 2.14.2

2011-07-14 Thread Urs Liska
Am 14.07.2011 16:18, schrieb Graham Percival: On Thu, Jul 14, 2011 at 06:53:45AM -0600, Carl Sorensen wrote: On 7/14/11 6:23 AM, Urs Liskalilyli...@googlemail.com wrote: ATM there are many issues to verify that are marked as fixed_2_14_2. So before this version is released the issues can't

Re: 2.14.2

2011-07-14 Thread Graham Percival
On Thu, Jul 14, 2011 at 04:30:30PM +0200, Urs Liska wrote: ick. That means that they're floating around in the issues to verify list, thereby confusing things for development. Do they really? After all they are issues to verify. With this policy you can see the tag verified_2_15_5 in the

\displayLilyMusic causes error with \addFingering from LSR 768

2011-07-14 Thread -Eluze
this code \version 2.15.5 \displayLilyMusic { \addFingering a #-5 } reports in the log: GNU LilyPond 2.15.5 Processing `test.ly' Parsing...ERROR: No applicable method for #extended-generic map (0) in call (map #procedure #f (tweak) #f) without \displayLilyMusic it works. cheers Eluze --

Re: 2.14.2

2011-07-14 Thread Dmytro O. Redchuk
On Thu 14 Jul 2011, 16:30 Urs Liska wrote: But OTOH one could also argue to leave such issues completely unverified if you can't verify them completely. I believe there is nothing wrong in either verifying partially or leaving untouched until mentioned binary release occurs. We are now doing

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

2011-07-14 Thread lilypond
Comment #2 on issue 1732 by carl.d.s...@gmail.com: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 I've set up a shell script to run this 100 times, and it ran successfully all 100 times with my shell script.

Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768

2011-07-14 Thread lilypond
Status: Accepted Owner: Labels: Type-Other Priority-Medium New issue 1764 by brownian.box: \displayLilyMusic causes error with \addFingering from LSR 768 http://code.google.com/p/lilypond/issues/detail?id=1764 Reported by Eluze,

Re: \displayLilyMusic causes error with \addFingering from LSR 768

2011-07-14 Thread Dmytro O. Redchuk
On Thu 14 Jul 2011, 07:58 -Eluze wrote: this code \version 2.15.5 \displayLilyMusic { \addFingering a #-5 } reports in the log: GNU LilyPond 2.15.5 Processing `test.ly' Parsing...ERROR: No applicable method for #extended-generic map (0) in call (map #procedure #f (tweak) #f)

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

2011-07-14 Thread lilypond
Comment #3 on issue 1732 by carl.d.s...@gmail.com: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 I'm at 200 runs with no error. For the record, here's the rest of the output when it succeeds: Preprocessing

Re: Issue 1721 in lilypond: Doc: translated docs should use @rlsrnamed instead of @rlsr

2011-07-14 Thread lilypond
Comment #3 on issue 1721 by paconet@gmail.com: Doc: translated docs should use @rlsrnamed instead of @rlsr http://code.google.com/p/lilypond/issues/detail?id=1721 @r*-named variants of the xref macros take an extra argument, the localized text for the link, so you can not batch fix

Re: Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768

2011-07-14 Thread lilypond
Updates: Status: Invalid Comment #1 on issue 1764 by n.putt...@gmail.com: \displayLilyMusic causes error with \addFingering from LSR 768 http://code.google.com/p/lilypond/issues/detail?id=1764 The LSR snippet is really at fault here; it shouldn't set 'tweaks to #f. Note that there

Partcombine: full bar rests

2011-07-14 Thread Jean-Charles Malahieude
Hi all! Using the part combiner, I would prefer not to have to split a multimeasure rest or use tags in order to get what is on the second line. --- \version 2.14.1 \partcombine \relative c' { R1 c R1*2 r4 c r2 \break R1 c R1 R1 r4 c r2 } \relative c' { R1*3 e1 R1 R1*3 e1 r4

Re: Issue 930 in lilypond: Collision: differently-sized noteheads in a polyphonic situation

2011-07-14 Thread lilypond
Comment #2 on issue 930 by n.putt...@gmail.com: Collision: differently-sized noteheads in a polyphonic situation http://code.google.com/p/lilypond/issues/detail?id=930 Another example from Werner, using cues: \addQuote clarinet \relative c' { f8 g a b c2 | c8 b a g f2 | } \new Staff

Re: Issue 1761 in lilypond: cue notes clash with main voice

2011-07-14 Thread lilypond
Updates: Status: Duplicate Mergedinto: 930 Comment #2 on issue 1761 by n.putt...@gmail.com: cue notes clash with main voice http://code.google.com/p/lilypond/issues/detail?id=1761 (No comment was entered for this change.) ___

Re: Issue 930 in lilypond: Collision: differently-sized noteheads in a polyphonic situation

2011-07-14 Thread lilypond
Comment #3 on issue 930 by n.putt...@gmail.com: Collision: differently-sized noteheads in a polyphonic situation http://code.google.com/p/lilypond/issues/detail?id=930 Issue 1761 has been merged into this issue. ___ bug-lilypond mailing list

Re: Issue 1763 in lilypond: OttavaBracket doesn't follow fontSize

2011-07-14 Thread lilypond
Comment #2 on issue 1763 by lemzw...@googlemail.com: OttavaBracket doesn't follow fontSize http://code.google.com/p/lilypond/issues/detail?id=1763 Silly me :-) ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1761 in lilypond: cue notes clash with main voice

2011-07-14 Thread lilypond
Comment #3 on issue 1761 by lemzw...@googlemail.com: cue notes clash with main voice http://code.google.com/p/lilypond/issues/detail?id=1761 Thanks. I was quite sure that this is a duplicate, but I haven't found the issue number. ___

Re: Issue 1761 in lilypond: cue notes clash with main voice

2011-07-14 Thread lilypond
Comment #4 on issue 1761 by n.putt...@gmail.com: cue notes clash with main voice http://code.google.com/p/lilypond/issues/detail?id=1761 No problem, it took me a while to find it. :) ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode

2011-07-14 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #10 on issue 1688 by pkx1...@gmail.com: New half-closed hihat symbol for drum mode http://code.google.com/p/lilypond/issues/detail?id=1688 No problems make and reg test comparison - is there no percussion reg test? :)

Re: Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768

2011-07-14 Thread -Eluze
lilypond-4 wrote: Updates: Status: Invalid Comment #1 on issue 1764 by n.putt...@gmail.com: \displayLilyMusic causes error with \addFingering from LSR 768 http://code.google.com/p/lilypond/issues/detail?id=1764 The LSR snippet is really at fault here; it shouldn't set 'tweaks

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

2011-07-14 Thread lilypond
Comment #4 on issue 1732 by joenee...@gmail.com: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 Does the attached patch help? Attachments: 0001-Fix-a-segfault-caused-by-improper-initialization-of-.patch