On Mon, Mar 26, 2012 at 2:49 PM, Lenore Horner <lenorehor...@sbcglobal.net>wrote:
> > I'm not top posting. > > \version "2.14.2" > \paper{ ragged-right=##t } > \relative c'' { > \set tupletSpannerDuration = #(ly:make-moment 1 4) \times > 2/3 { > \repeat percent 2 {g8 f g f g f g f g f g f } > } \unset tupletSpannerDuration > } > > Produces correct pdf output but also the following string of error messages > (the full piece of music showed similar inconvenient lack of line numbers > with the errors). > > /Applications/LilyPond.app/Contents/Resources/bin/lilypond > tuplet-repeatPercent-bug.ly; > open tuplet-repeatPercent-bug.pdf > GNU LilyPond 2.14.2 > Processing `tuplet-repeatPercent-bug.ly' > Parsing... > Interpreting music... > programming error: stopped tuplet bracket has neither left nor right bound > continuing, cross fingers > programming error: stopped tuplet bracket has neither left nor right bound > continuing, cross fingers > programming error: stopped tuplet bracket has neither left nor right bound > continuing, cross fingers > programming error: stopped tuplet bracket has neither left nor right bound > continuing, cross fingers > Preprocessing graphical objects... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Layout output to `tuplet-repeatPercent-bug.ps'... > Converting to `./tuplet-repeatPercent-bug.pdf'... > success: Compilation successfully completed > > > This > \version "2.14.2" > \paper{ ragged-right=##t } > \relative c'' { > \repeat percent 2 {\set tupletSpannerDuration = #(ly:make-moment 1 4) > \times 2/3 { > g8 f g f g f g f g f g f > } \unset tupletSpannerDuration } > } > > produces identical music but no error complaints, however in long passages > of > triplets it's a nuisance to have to stop and start the > tupletSpannerDuration > for chunks involving % repeats. > > NOTE: I've had to wack things at 80-characters so some of the output isn't > completely accurate. Greetings, Lenore Horner and list members - Thanks for the bug notification. I'm entering this as an enhancement, rather than a defect, since LilyPond *does* currently produce the correct output, although not as simply as would be desired. The request has been entered as issue 2439 : http://code.google.com/p/lilypond/issues/detail?id=2439 All the best, Ralph _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond