"Wrong type" with polyphony, manual beams, dotted rests and notes

This one is weird. Apparently some combinations of polyphony, manual beams, and a dotted rest followed by a note, trigger a "Wrong type" error (Windows XP here). Many variations I've tried still trigger the error, while other variations don't. You can experiment for yourself. Unlike the stemlets-o

Re: no compile on version 2.11.43 for Windows XP

Can you try 2.11.43-2 (uploaded today)? 2008/3/26, Tom Richard <[EMAIL PROTECTED]>: > Version 2.10.33 for Windows XP compiles great. I have tried re-installing > 2.11.43 3 times, carefully un-installing previous version every time. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.n

Re: no compile on version 2.11.43 for Windows XP

Yes it's a known problem with 2.11.43. You can use download and 2.11.42 from http://download.linuxaudio.org/lilypond/binaries/mingw/ while waiting for a new working version. /Mats Tom Richard wrote: Version 2.10.33 for Windows XP compiles great. I have tried re-installing 2.11.43 3 times, ca

no compile on version 2.11.43 for Windows XP

Version 2.10.33 for Windows XP compiles great. I have tried re-installing 2.11.43 3 times, carefully un-installing previous version every time. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 493 in lilypond: Text spanners and trills do not obey 'to-barline

Issue 493: Text spanners and trills do not obey 'to-barline http://code.google.com/p/lilypond/issues/detail?id=493 Comment #4 by gpermus: - how does the png look? - if all else fails, print an example. PDF viewers lie. :) -- You received this message because you are listed in the owner or CC

Issue 554 in lilypond: Pitched rests collide with accidentals

Issue 554: Pitched rests collide with accidentals http://code.google.com/p/lilypond/issues/detail?id=554 Comment #5 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC

Issue 577 in lilypond: Regression: strict-grace-spacing is broken when not using ragged-right

Issue 577: Regression: strict-grace-spacing is broken when not using ragged-right http://code.google.com/p/lilypond/issues/detail?id=577 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because

Issue 553 in lilypond: break-align-symbols alignment bug when using c major key-signature

Issue 553: break-align-symbols alignment bug when using c major key-signature http://code.google.com/p/lilypond/issues/detail?id=553 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you a

Issue 550 in lilypond: input/regression/page-turn-page-breaking-auto-first-page.ly

Issue 550: input/regression/page-turn-page-breaking-auto-first-page.ly http://code.google.com/p/lilypond/issues/detail?id=550 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are list

Issue 493 in lilypond: Text spanners and trills do not obey 'to-barline

Issue 493: Text spanners and trills do not obey 'to-barline http://code.google.com/p/lilypond/issues/detail?id=493 Comment #3 by v.villenave: It seems to be fixed (however, depending on the PDF viewer I use, the Spanner is not always printed correctly). Issue attribute updates: Status

Issue 475 in lilypond: Scripts influence horizontal alignment of trill spanners

Issue 475: Scripts influence horizontal alignment of trill spanners http://code.google.com/p/lilypond/issues/detail?id=475 Comment #2 by v.villenave: Indeed. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this

Issue 473 in lilypond: trills slightly non-centered

Issue 473: trills slightly non-centered http://code.google.com/p/lilypond/issues/detail?id=473 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of

Issue 339 in lilypond: possibly misplaced dot in notehead collision

Issue 339: possibly misplaced dot in notehead collision http://code.google.com/p/lilypond/issues/detail?id=339 Comment #5 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner

Issue 587 in lilypond: Segfault: \acciaccatura inside \times when using \new Staff

Issue 587: Segfault: \acciaccatura inside \times when using \new Staff http://code.google.com/p/lilypond/issues/detail?id=587 Comment #3 by v.villenave: Perfect! Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of t

Re: stemlets + beamed rests = crash (2.10.33, windows)

I can confirm that it gives a segmentation fault with version 2.10.33 also in Linux. In version 2.11, on the other hand, you don't get any crash, even though the resulting layout may need some extra tweaking. /Mats Marcus Macauley wrote: \version "2.10.33" \paper{ ragged-right=##t } { % Li