2012/10/4 Eluze <elu...@gmail.com>: > Thomas Morley wrote >> 2012/10/2 Eluze < > >> eluzew@ > >> >: >> >> But I think there are likely some more. > > here is the list of all the snippets I found causing problems (searching for > "error:|warning:|wrong|pair\):"): > > > a-function-to-repeatedly-print-a-given-pattern-with-different-notes > affecting-items-only-on-the-left-or-rigth-of-a-linebreak-barlines,-keysignatures,-clefs-etc. > ancient-accidentals > autochange-music-with-a-different-pitch > autochange-music-with-a-different-pitch > bar-chords-notation-for-guitar--with-text-spanner > baroque-slash-ornaments-between-chords > chord-names-and-lyrics-without-a-staff > creating-a-schenker-graph > creating-a-sequence-of-notes-on-various-pitches > creating-music-with-scheme-music-box > defining-an-engraver-in-scheme--ambitus-engraver > dynamics-custom-text-spanner-postfix > dynamics-text-spanner-postfix > easy-rhythm-template-creation > engravers-one-by-one > engraving-symmetric-or-palindromical-music > file-information > flams,-drags-and-ruffs > forcing-visibility-of-the-first-bar-number > function-to-create-wygiwym-chord-names > grid-lines--emphasizing-rhythms-and-notes-synchronization > hymn-template-for-per-voice-music-and--partcombine > irrational-time-signatures-for-metric-modulation > normalized--transposition > positioning-two-opposite--fermata-signs-over-the-last-bar-line > printing-only-odd-bar-numbers > removing-items-from-only-voicetwo-using-a-scheme-filter > ripped,-torn-staff-lines > satb-choir-template-hymn-template-two-staves---one-text-for-all-voices > score-for-diatonic-accordion > shortening-volta-brackets > suppressing-warnings-for-clashing-note-columns > using-non-standard-clef-positions-and-adding-customized-clef-definitions > > if you need the logs I can provide them > > Eluze > > > > -- > View this message in context: > http://lilypond.1069038.n5.nabble.com/LSR-is-not-at-the-stable-release-level-tp133838p134100.html > Sent from the Bugs mailing list archive at Nabble.com. > > _______________________________________________ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi Eluze, seems you *really* want the LSR at 2.16. :) There are two reasons not to update now: a) 2.16. not in distros (already under discussion here and in an other thread) b) It seems that _any_ change to the code of a snippet will result in a strange LSR-image. That was the reason I stopped adding commented 2.16.-code, as I mentioned before. So, what should we do? Any Idea? -Harm _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
