Re: Issue 1209 in lilypond: beatLength is no longer used, but still appears in regression tests converted from xml

Updates: Status: Verified Comment #6 on issue 1209 by percival.music.ca: beatLength is no longer used, but still appears in regression tests converted from xml http://code.google.com/p/lilypond/issues/detail?id=1209 sometimes the build system doesn't update files properly? :) The

Re: Issue 1119 in lilypond: [PATCH] fix ly:parser-parse-file in an ly file (issue1345041)

Updates: Status: Verified Mergedinto: -1096 Comment #2 on issue 1119 by percival.music.ca: [PATCH] fix ly:parser-parse-file in an ly file (issue1345041) http://code.google.com/p/lilypond/issues/detail?id=1119 This patch is definitely discussed in 1096, so the duplicate is

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

Updates: Summary: fix for 1112 produces bad page breaking in make test and doc Owner: joeneeman Comment #11 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 ok, an hour of

Time off

Dear fellow Bug Squad members, I'm sorry to tell that - due to heavy duty doing packing for four persons - I won't have the time to spend my fifteen minutes today. Furthermore I will be off the upcoming two Fridays until August 27. After that I'll be back and do my duty - based on experience

Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion

Updates: Labels: Patch Comment #5 on issue 839 by Carl.D.Sorensen: Enhancement: improving midi2ly conversion http://code.google.com/p/lilypond/issues/detail?id=839 Has anybody reviewed this patch? ___ bug-lilypond mailing list

Re: Issue 928 in lilypond: `Dynamics' items aren't vertically centered

Comment #4 on issue 928 by Carl.D.Sorensen: `Dynamics' items aren't vertically centered http://code.google.com/p/lilypond/issues/detail?id=928 Comparing the first image with the second causes me to believe that this issue should be marked fixed and closed. If we need to start a new issue

Re: Issue 1041 in lilypond: Output suffix for score should be documented

Updates: Labels: -Priority-Critical Priority-Medium Comment #5 on issue 1041 by percival.music.ca: Output suffix for score should be documented http://code.google.com/p/lilypond/issues/detail?id=1041 On second thought, since this feature wasn't present in 2.12, a failure to

Re: Issue 818 in lilypond: Bus error when adding Instrument_name_engraver to StaffGroup and outputting MIDI.

Updates: Labels: -OpSys-Windows Comment #11 on issue 818 by percival.music.ca: Bus error when adding Instrument_name_engraver to StaffGroup and outputting MIDI. http://code.google.com/p/lilypond/issues/detail?id=818 Good news, everyone! The original snippet segfaults with lilypond

Re: DynamicTextSpanners should end like hairpins

On Thu, Aug 12, 2010 at 10:42 PM, Neil Puttock n.putt...@gmail.com wrote: On 12 August 2010 18:18, Phil Holmes m...@philholmes.net wrote: I'm assuming that \cresc etc. are new features of 2.13? No, these are unchanged, though the spacing is better in 2.13 since hairpins used to collide with

Re: Time off

On Fri, Aug 13, 2010 at 10:57 AM, Urs Liska lilyli...@googlemail.com wrote: I'm sorry to tell that - due to heavy duty doing packing for four persons - I won't have the time to spend my fifteen minutes today. Furthermore I will be off the upcoming two Fridays until August 27. After that I'll

Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins

Status: Accepted Owner: Labels: Type-Enhancement Priority-Medium New issue 1216 by PhilEHolmes: DynamicTextSpanners should end like hairpins http://code.google.com/p/lilypond/issues/detail?id=1216 From Jon Arnold: DynamicTextSpanners in their current state will prevent hairpins from being

Re: DynamicTextSpanners should end like hairpins

Jon Arnold jonarnoldsem...@gmail.com wrote in message news:loom.20100811t213232-...@post.gmane.org... I'm not top posting. DynamicTextSpanners in their current state will prevent hairpins from being produced properly if the space is small. The DynamicTextSpanner should have the same right

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

Comment #1 on issue 1216 by percival.music.ca: DynamicTextSpanners should end like hairpins http://code.google.com/p/lilypond/issues/detail?id=1216 Didn't Neil have a programming comment about this? I would definitely include information from developers with this enhancement request.

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

Comment #2 on issue 1216 by PhilEHolmes: DynamicTextSpanners should end like hairpins http://code.google.com/p/lilypond/issues/detail?id=1216 Here's the information from Neil: The issue here isn't the DynamicTextSpanner; it's the code which spaces a hairpin depending on the objects found at

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

Comment #3 on issue 1216 by jonarnoldsemail: DynamicTextSpanners should end like hairpins http://code.google.com/p/lilypond/issues/detail?id=1216 So, it sounds like the hairpin code needs to treat spanners like hairpins? In the meantime, what's the best workaround? Decreasing the

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

Comment #12 on issue 1201 by joeneeman: fix for 1112 produces bad page breaking in make test and doc http://code.google.com/p/lilypond/issues/detail?id=1201 I can't reproduce (ie. it just works on one page for me), but I've pushed something that should fix it.

Re: Issue 1084 in lilypond: lilypond-book fails on identical snippets

Updates: Status: Fixed Labels: fixed_2_13_30 Comment #5 on issue 1084 by joeneeman: lilypond-book fails on identical snippets http://code.google.com/p/lilypond/issues/detail?id=1084 (No comment was entered for this change.) ___

Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0.

Status: Accepted Owner: Labels: Type-Documentation Priority-High Maintainability Frog New issue 1217 by percival.music.ca: clean up undocumented regtests in 2.14.0. http://code.google.com/p/lilypond/issues/detail?id=1217 Strictly speaking, we shouldn't hold up 2.14 if a new feature in

Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests

Updates: Summary: ensure that no information about 2.12.3 features is only in the regtests Comment #18 on issue 989 by percival.music.ca: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 As Han-Wen pointed

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

Updates: Status: Fixed Comment #13 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 Curse you... I was just about to go to bed when I saw your commit. You forced me to get

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

Comment #14 on issue 1201 by joeneeman: fix for 1112 produces bad page breaking in make test and doc http://code.google.com/p/lilypond/issues/detail?id=1201 Oops, sorry :) I hope you aren't staying up to wait for the build to finish ___

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

Comment #15 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 Well, I'm officially still jetlagged (I woke up at 7.30 this morning -- as a graduate student, I really shouldn't be waking

Re: Issue 1098 in lilypond: Unable to print long scores

Updates: Status: Invalid Comment #5 on issue 1098 by percival.music.ca: Unable to print long scores http://code.google.com/p/lilypond/issues/detail?id=1098 We don't have an example, and nobody has touched this since May, so marking it invalid.

Re: Issue 818 in lilypond: Bus error when adding Instrument_name_engraver to StaffGroup and outputting MIDI.

Comment #12 on issue 818 by n.puttock: Bus error when adding Instrument_name_engraver to StaffGroup and outputting MIDI. http://code.google.com/p/lilypond/issues/detail?id=818 Hmm, that is interesting. I've just tested it in VirtualBox, and get the same result. TBH, I'm pretty stumped

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

Comment #4 on issue 1216 by n.puttock: DynamicTextSpanners should end like hairpins http://code.google.com/p/lilypond/issues/detail?id=1216 So, it sounds like the hairpin code needs to treat spanners like hairpins? Nope, that would make things worse: the padding between adjacent hairpins

Re: Issue 1208 in lilypond: minor regression: Some combination of 'staff-affinity for two Lyrics may cause unwanted vertical space

Updates: Status: Invalid Comment #2 on issue 1208 by Carl.D.Sorensen: minor regression: Some combination of 'staff-affinity for two Lyrics may cause unwanted vertical space http://code.google.com/p/lilypond/issues/detail?id=1208 This is a deliberate change intended to enforce a

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

Updates: Status: Fixed Labels: fixed_2_13_31 Comment #4 on issue 1124 by pnorcks: implement \eyeglasses using a 'path expression http://code.google.com/p/lilypond/issues/detail?id=1124 Pushed:

Re: Issue 1125 in lilypond: implement a \path markup command

Updates: Status: Fixed Labels: fixed_2_13_31 Comment #3 on issue 1125 by pnorcks: implement a \path markup command http://code.google.com/p/lilypond/issues/detail?id=1125 Pushed:

Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN

Comment #1 on issue 1161 by Carl.D.Sorensen: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN http://code.google.com/p/lilypond/issues/detail?id=1161 I think the new lyrics minimum spacing default has greatly improved the situation. This is

Re: Issue 1198 in lilypond: Display method for \time broken

Updates: Status: Fixed Labels: fixed_2_13_30 Comment #4 on issue 1198 by Carl.D.Sorensen: Display method for \time broken http://code.google.com/p/lilypond/issues/detail?id=1198 Patch is now pushed. ___ bug-lilypond mailing list

Re: Issue 928 in lilypond: `Dynamics' items aren't vertically centered

Updates: Status: Verified Comment #5 on issue 928 by v.villenave: `Dynamics' items aren't vertically centered http://code.google.com/p/lilypond/issues/detail?id=928 Indeed. Carl, you're right: this issue has to be closed. I'm not even sure if it's worth opening a new one, since I'm

Re: Issue 1098 in lilypond: Unable to print long scores

Updates: Status: New Owner: v.villenave Comment #6 on issue 1098 by v.villenave: Unable to print long scores http://code.google.com/p/lilypond/issues/detail?id=1098 I wasn't able to reproduce it, actually, but I remember having seen such errors when compiling my opera on a

Re: Issue 818 in lilypond: Bus error when adding Instrument_name_engraver to StaffGroup and outputting MIDI.

Comment #13 on issue 818 by Carl.D.Sorensen: Bus error when adding Instrument_name_engraver to StaffGroup and outputting MIDI. http://code.google.com/p/lilypond/issues/detail?id=818 This still runs fine under 2.13.29 on OSX 10.5 ___ bug-lilypond

Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work

Comment #4 on issue 1214 by pnorcks: Cue notes to music that creates a sub-voice does not work http://code.google.com/p/lilypond/issues/detail?id=1214 Please ignore my previous comment. The problem lies elsewhere, possibly in quote-iterator.cc.

Re: Issue 1198 in lilypond: Display method for \time broken

Updates: Labels: -fixed_2_13_30 fixed_2_13_31 Comment #5 on issue 1198 by Carl.D.Sorensen: Display method for \time broken http://code.google.com/p/lilypond/issues/detail?id=1198 Oops -- missed the new release ___ bug-lilypond mailing list

Re: Issue 1104 in lilypond: Enhancement: 'offset for \underline markup function needed (and proposed)

Updates: Status: Fixed Owner: kie...@alumni.rice.edu Labels: fixed_2_13_31 Comment #5 on issue 1104 by pnorcks: Enhancement: 'offset for \underline markup function needed (and proposed) http://code.google.com/p/lilypond/issues/detail?id=1104 This has been pushed:

Re: Issue 956 in lilypond: Win LilyPad editor About message could be improved

Updates: Status: Accepted Owner: --- Comment #2 on issue 956 by pnorcks: Win LilyPad editor About message could be improved http://code.google.com/p/lilypond/issues/detail?id=956 (No comment was entered for this change.) ___

Re: Issue 534 in lilypond: two problems with win32 notepad clone

Updates: Status: Accepted Owner: --- Labels: -Priority-Low Priority-Postponed Comment #4 on issue 534 by pnorcks: two problems with win32 notepad clone http://code.google.com/p/lilypond/issues/detail?id=534 All LilyPad issues are postponed, since it looks like we would

Re: Issue 431 in lilypond: menus in windows should be unicode

Updates: Status: Accepted Owner: --- Labels: -Priority-Low Priority-Postponed Comment #2 on issue 431 by pnorcks: menus in windows should be unicode http://code.google.com/p/lilypond/issues/detail?id=431 (No comment was entered for this change.)

Re: Issue 908 in lilypond: ImageMagick `compare' commands need some investigating

Updates: Owner: --- Comment #5 on issue 908 by pnorcks: ImageMagick `compare' commands need some investigating http://code.google.com/p/lilypond/issues/detail?id=908 (No comment was entered for this change.) ___ bug-lilypond mailing list

Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion

Updates: Owner: --- Comment #6 on issue 839 by pnorcks: Enhancement: improving midi2ly conversion http://code.google.com/p/lilypond/issues/detail?id=839 Yes, John posted a review to MIDI Lilynet list:

Re: Issue 817 in lilypond: Enhancement: new syntax for more flexible cresc/dim spanners

Updates: Owner: reinhold.kainhofer Cc: -reinhold.kainhofer -n.puttock -pnorcks Comment #4 on issue 817 by pnorcks: Enhancement: new syntax for more flexible cresc/dim spanners http://code.google.com/p/lilypond/issues/detail?id=817 I'm a little confused about the status of

Re: Issue 720 in lilypond: incorrect bbox values for EPS images

Comment #2 on issue 720 by pnorcks: incorrect bbox values for EPS images http://code.google.com/p/lilypond/issues/detail?id=720 I can't reproduce this problem with latest git. Or rather, I may be using different options/commands, but I'll list what I have done: 1) Run `lilypond -dpreview

Re: Issue 695 in lilypond: slurs may take too much vertical extent

Updates: Owner: --- Comment #1 on issue 695 by pnorcks: slurs may take too much vertical extent http://code.google.com/p/lilypond/issues/detail?id=695 (No comment was entered for this change.) Attachments: bug.preview.png 1.7 KB

Re: Issue 695 in lilypond: slurs may take too much vertical extent

Updates: Labels: -Engraving-nitpick Comment #2 on issue 695 by pnorcks: slurs may take too much vertical extent http://code.google.com/p/lilypond/issues/detail?id=695 (No comment was entered for this change.) ___ bug-lilypond mailing list

Re: Issue 692 in lilypond: slurs look bad when forced on the same direction as the stems

Updates: Owner: --- Labels: -Engraving-nitpick Comment #2 on issue 692 by pnorcks: slurs look bad when forced on the same direction as the stems http://code.google.com/p/lilypond/issues/detail?id=692 (No comment was entered for this change.)