[PATCH] Fix `split-at-predicate' in `scm/lily-library.scm'.

2009-11-09 Thread Thomas
Don't make the assumption that if `(PRED previous_element element)' is false, `(PRED element previous_element)' must be true. Suppose we want to split `(1 2 3 5 7)' into two lists such that the first list contains the initial consecutive integers `(1 2 3)' and the second contains the remaining ele

bar-chords-notation-for-guitar--with-text-spanner.ly doesn't compile on OS X

2009-11-09 Thread Harmath Dénes
On OS X 10.5.8 (Linux works well), LilyPond 2.13.7 can't compile Documentation/snippets/bar-chords-notation-for-guitar--with-text-spanner.ly: thSoft-MacBook:Temp thsoft$ /Applications/LilyPond-dev.app/Contents/Resources/bin/lilypond bar-chords-notation-for-guitar--with-text-spanner.ly GNU LilyPon

Re: Issue 800 melisma extenders

2009-11-09 Thread Chris Snyder
Nicolas Sceaux wrote: >> In my opinion, the issue it addressed is much more annoying than >> regression > > I beg to disagree: it fixes a special case, but breaks extender lines in > general. I disagree here - the cases where I encountered the bug were not anything out of the ordinary (it's quit

Re: Issue 800 melisma extenders

2009-11-09 Thread Nicolas Sceaux
Le 9 nov. 2009 à 19:43, Chris Snyder a écrit : Nicolas Sceaux wrote: > Hi, > > As was reported on > a regression was introduced by patch > 7531ea6b3bb254f4d82aabde347a91671533b45a: > > Fix lyric extenders to end properly when there

Re: Issue 800 melisma extenders

2009-11-09 Thread Chris Snyder
Nicolas Sceaux wrote: > Hi, > > As was reported on > a regression was introduced by patch > 7531ea6b3bb254f4d82aabde347a91671533b45a: > > Fix lyric extenders to end properly when there are notes but no more > lyrics. > > As this patch

Issue 800 melisma extenders

2009-11-09 Thread Nicolas Sceaux
Hi, As was reported on a regression was introduced by patch 7531ea6b3bb254f4d82aabde347a91671533b45a: Fix lyric extenders to end properly when there are notes but no more lyrics. The previous extender code only ends extend

Re: Bad spacing (gap) when large interval and accidental

2009-11-09 Thread Carl Sorensen
On 11/7/09 3:08 PM, "Hudson Lacerda" wrote: > Hi. The code below results in a gap between the last notes. > There is enough room below "d" (bottom staff) to draw the sharp of "fis". > > P.S.: Concerning to "beams should not collide with accidentals" issue (#76), I > think the clashes are a aw