Re: Issue 1060 in lilypond: Add Funk-style shape note heads

Updates: Labels: Patch Comment #39 on issue 1060 by neziap: Add Funk-style shape note heads http://code.google.com/p/lilypond/issues/detail?id=1060 http://lists.gnu.org/archive/html/lilypond-devel/2010-07/msg00385.html ___ bug-lilypond

Re: Issue 1117 in lilypond: Patch: Woodwind diagrams in the NR

Comment #4 on issue 1117 by v.villenave: Patch: Woodwind diagrams in the NR http://code.google.com/p/lilypond/issues/detail?id=1117 Mike and I had a chat about it, he will update the doc himself within a few weeks but doesn't seem to need a special tracker page to pester him about it.

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

Updates: Status: Started Owner: --- Labels: -Priority-Postponed Priority-Medium Comment #16 on issue 687 by v.villenave: Enhancement: inequal MIDI quantization of equal durations (swing, rubato) http://code.google.com/p/lilypond/issues/detail?id=687 Perhaps we

Re: Issue 1210 in lilypond: beatLength is no longer used, but still appears in a snippet

Updates: Status: Verified Comment #3 on issue 1210 by v.villenave: beatLength is no longer used, but still appears in a snippet http://code.google.com/p/lilypond/issues/detail?id=1210 Closing. ___ bug-lilypond mailing list

Re: Issue 1201 in lilypond: regtest building flakey?

Updates: Status: Verified Mergedinto: -1209 Comment #8 on issue 1201 by v.villenave: regtest building flakey? http://code.google.com/p/lilypond/issues/detail?id=1201 ... and Verifying the Duplicate. ___ bug-lilypond mailing list

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

Comment #4 on issue 1209 by v.villenave: beatLength is no longer used, but still appears in regression tests converted from xml http://code.google.com/p/lilypond/issues/detail?id=1209 Issue 1201 has been merged into this issue. ___ bug-lilypond

Re: Issue 1201 in lilypond: regtest building flakey?

Updates: Status: Duplicate Mergedinto: 1209 Comment #7 on issue 1201 by v.villenave: regtest building flakey? http://code.google.com/p/lilypond/issues/detail?id=1201 OK, so this is now issue 1209. Closing this one. ___ bug-lilypond

Re: Issue 1213 in lilypond: Segmentation fault : extender triggers an infinite loop in Context::now_mom ()

Comment #1 on issue 1213 by v.villenave: Segmentation fault : extender triggers an infinite loop in Context::now_mom () http://code.google.com/p/lilypond/issues/detail?id=1213 Interesting. This seems to have been fixed in the 2.13 branch; what do we do in such a case? Can we close this

Re: Issue 1201 in lilypond: regtest building flakey?

Updates: Status: Accepted Comment #9 on issue 1201 by percival.music.ca: regtest building flakey? http://code.google.com/p/lilypond/issues/detail?id=1201 WTF?! Valentin, this has *nothing* to do with beatlength. Something is seriously wrong with either the spacing code, or with the

Issue 1215 in lilypond: Woodwind diagrams in the NR

Status: Started Owner: Labels: Type-Documentation Priority-Medium New issue 1215 by percival.music.ca: Woodwind diagrams in the NR http://code.google.com/p/lilypond/issues/detail?id=1215 We need documentation for woodwind diagrams. This is a new feature since 2.13, so it doesn't block a

Re: Issue 1117 in lilypond: Patch: Woodwind diagrams

Updates: Summary: Patch: Woodwind diagrams Comment #5 on issue 1117 by percival.music.ca: Patch: Woodwind diagrams http://code.google.com/p/lilypond/issues/detail?id=1117 That's nice, but the tracker isn't for his convenience alone. It's used to organize all lilypond development.

Re: Issue 1214 in lilypond: Problem with \cueDuring and \new CueVoice in parallel music

Comment #1 on issue 1214 by percival.music.ca: Problem with \cueDuring and \new CueVoice in parallel music http://code.google.com/p/lilypond/issues/detail?id=1214 Trying to compile this produces an error message. Could somebody clean up the example and upload a png showing the problem?

Re: Issue 1213 in lilypond: Segmentation fault : extender triggers an infinite loop in Context::now_mom ()

Updates: Labels: Priority-Postponed Comment #2 on issue 1213 by percival.music.ca: Segmentation fault : extender triggers an infinite loop in Context::now_mom () http://code.google.com/p/lilypond/issues/detail?id=1213 Hmm. I see why Ralph didn't give it a priority. :) Honestly,

Re: Issue 1167 in lilypond: link from manuals HTML pages back to website

Updates: Status: Fixed Labels: fixed_2_13_30 Comment #3 on issue 1167 by percival.music.ca: link from manuals HTML pages back to website http://code.google.com/p/lilypond/issues/detail?id=1167 Pushed as 76e305393723a8e1b289e19641c059bc394c5195

Re: full-measure rests don't seem to reserve adequate space

Neil == Neil Puttock n.putt...@gmail.com writes: Neil On 11 August 2010 22:01, Laura Conrad lcon...@laymusic.org wrote: The attached file should have 4 full-measure rests, but in fact looks to the casual user like there are only three. A workaround is to make sure

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 1214 in lilypond: Cue notes to music that creates a sub-voice does not work

Updates: Summary: Cue notes to music that creates a sub-voice does not work Labels: Priority-Medium Comment #2 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 As Reinhold noted, this

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

Comment #3 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 The bug occurs because `recording-group-emulate' (scm/part-combiner.scm) returns a list that is inappropriate for using in `add-quotable'.

Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel

Comment #17 on issue 1096 by n.puttock: ly:parser-parse-string segfaults when directly called at toplevel http://code.google.com/p/lilypond/issues/detail?id=1096 parser_error doesn't generate a syntax error: music.ly:1:0: error: Display a helpful message to the user.

Re: Issue 1201 in lilypond: regtest building flakey?

Comment #10 on issue 1201 by v.villenave: regtest building flakey? http://code.google.com/p/lilypond/issues/detail?id=1201 Oh, sorry about the noise. Comment 6 led me to believe said 4 beatLength files were the issue. ___ bug-lilypond mailing

Re: full-measure rests don't seem to reserve adequate space

On 12 August 2010 17:34, Laura Conrad lcon...@laymusic.org wrote: That works.  Can anyone explain what the difference between:     \set Score.defaultBarType = and        \set Score.defaultBarType = empty is? The former only has an empty horizontal extent, whereas the latter is a

Re: DynamicTextSpanners should end like hairpins

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 text spans. The issue here isn't the DynamicTextSpanner; it's the code which

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

Updates: Status: Invalid Comment #5 on issue 1209 by Carl.D.Sorensen: beatLength is no longer used, but still appears in regression tests converted from xml http://code.google.com/p/lilypond/issues/detail?id=1209 The snippets in question work on a clean build from 2.13.29. I think

Re: Issue 1203 in lilypond: Page_turn_engraver refuses to break at R1*12, crams notes and produces blank page in the middle of score.

Updates: Status: Fixed Owner: joeneeman Labels: fixed_2_13_30 Comment #1 on issue 1203 by n.puttock: Page_turn_engraver refuses to break at R1*12, crams notes and produces blank page in the middle of score. http://code.google.com/p/lilypond/issues/detail?id=1203 (No

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

Updates: Summary: [PATCH] Add scheme binding for chain_callback (issue1890044) Status: Fixed Labels: fixed_2_13_30 Comment #1 on issue 1212 by n.puttock: [PATCH] Add scheme binding for chain_callback (issue1890044)

Re: Issue 994 in lilypond: Enhancement: the ability to automatically beam across rests.

Updates: Status: Started Owner: n.puttock Comment #1 on issue 994 by n.puttock: Enhancement: the ability to automatically beam across rests. http://code.google.com/p/lilypond/issues/detail?id=994 (No comment was entered for this change.)

Re: Issue 1205 in lilypond: Enhancement request: Repeating \tempo marks should be displayable in a controllable way

Updates: Status: Started Owner: n.puttock Comment #2 on issue 1205 by n.puttock: Enhancement request: Repeating \tempo marks should be displayable in a controllable way http://code.google.com/p/lilypond/issues/detail?id=1205 (No comment was entered for this change.)

Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob

Updates: Status: Fixed Labels: fixed_2_13_30 Comment #4 on issue 1063 by Carl.D.Sorensen: Reverting nested property fails to restore default value if preceded by override in same grob http://code.google.com/p/lilypond/issues/detail?id=1063 Thanks for the fix, Rodolfo!

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

Updates: Labels: Patch Comment #3 on issue 1198 by Carl.D.Sorensen: Display method for \time broken http://code.google.com/p/lilypond/issues/detail?id=1198 Patch is up for review on Rietveld: http://codereview.appspot.com/1986042/show ___

Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel

Updates: Owner: n.puttock Comment #18 on issue 1096 by Carl.D.Sorensen: ly:parser-parse-string segfaults when directly called at toplevel http://code.google.com/p/lilypond/issues/detail?id=1096 Neil's following this now, so I made him the owner

Re: Issue 612 in lilypond: spacing problem in tied chords with accidentals

Updates: Labels: Patch Comment #5 on issue 612 by Carl.D.Sorensen: spacing problem in tied chords with accidentals http://code.google.com/p/lilypond/issues/detail?id=612 The patch that csnyder put together on Rietveld got some feedback from Joe, but never got finished. The Rietveld