Re: programming errors: "Object is not a markup." and "I am not spanned!"
Wilbert Berendsen writes:
> Op donderdag 30 september 2010 schreef Marnix:
>
>> L.S.,
>>
>> For the following file
>>
>> \version "2.12.4"
>> { R\breve\fermata }
>
> use R\breve-\fermataMarkup (see the docs about full measure rests).
>
>> Even more alarming-looking,
>>
>> \version "2.12.4"
>> { R2 }
>>
>> results in a (correct) "barcheck failed" warning, but also in an "I am not
>> spanned!" error:
>
> R2 does not fill the measure that's why the MultiMeasureRest complains.
> No LilyPond bugs as far as I can tell.
Incomprehensible error messages count as bugs.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: programming errors: "Object is not a markup." and "I am not spanned!"
Op donderdag 30 september 2010 schreef Marnix:
> L.S.,
>
> For the following file
>
> \version "2.12.4"
> { R\breve\fermata }
use R\breve-\fermataMarkup (see the docs about full measure rests).
> Even more alarming-looking,
>
> \version "2.12.4"
> { R2 }
>
> results in a (correct) "barcheck failed" warning, but also in an "I am not
> spanned!" error:
R2 does not fill the measure that's why the MultiMeasureRest complains.
No LilyPond bugs as far as I can tell.
best regards,
Wilbert Berendsen
--
Frescobaldi, LilyPond editor for KDE: http://www.frescobaldi.org/
Nederlands LilyPond forum: http://www.lilypondforum.nl/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Skyline compaction is going overboard sometimes.
Check the first two systems on the second page of the following score:
\repeat unfold 80 { c' c' }
Perhaps skylines should not be taken as literally as that, but padded
out somewhat.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond crash
"Graham Percival" wrote in message news:20101002172122.ga22...@futoi... On Sat, Oct 02, 2010 at 06:02:19PM +0100, Phil Holmes wrote: On my Windows machine, Lilypond stops working at the "Preprocessing graphical objects" stage. Might be an oddity of my PC and how I run Lilypond, but don't reckon it should. Where does the cutoff seem to be? i.e. try 200, 400, 600, 800...? Also, as you certain that it *crashes*, or does it just take a long time? Try timing the code at 200, 400, 600, 800, etc -- look for a pattern, and if you see a pattern, you might be able to predict that (for example) it should take lilypond 5000 hours to complete the example you gave it. Cheers, - Graham Windows reports that Lilypond has stopped working. It's not timing out. Further experiments tomorrow - I'm on cooking duty currently. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond crash
On Sat, Oct 02, 2010 at 06:02:19PM +0100, Phil Holmes wrote: > On my Windows machine, Lilypond stops working at the "Preprocessing > graphical objects" stage. Might be an oddity of my PC and how I run > Lilypond, but don't reckon it should. Where does the cutoff seem to be? i.e. try 200, 400, 600, 800...? Also, as you certain that it *crashes*, or does it just take a long time? Try timing the code at 200, 400, 600, 800, etc -- look for a pattern, and if you see a pattern, you might be able to predict that (for example) it should take lilypond 5000 hours to complete the example you gave it. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Lilypond crash
Exploring the question of whether "random" music stresses Lilypond more than
repeated same code, I tried this:
\repeat unfold 2400 {
c''4 c' c c,
}
On my Windows machine, Lilypond stops working at the "Preprocessing
graphical objects" stage. Might be an oddity of my PC and how I run
Lilypond, but don't reckon it should.
Same for 2.12.3 and 2.13.35.
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning
Updates: Labels: Priority-Low Comment #2 on issue 1228 by percival.music.ca: \override RestCollision #'positioning-done = #merge-rests-on-positioning http://code.google.com/p/lilypond/issues/detail?id=1228 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1255 in lilypond: Add prefix to lyrics - extract hyphen dimensions or hyphen glyph from the font
Updates: Labels: -Type-Other Type-Enhancement Priority-Low Comment #3 on issue 1255 by percival.music.ca: Add prefix to lyrics - extract hyphen dimensions or hyphen glyph from the font http://code.google.com/p/lilypond/issues/detail?id=1255 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 766 in lilypond: Indent should automatically adapt to instrument names' length.
Issue 766: Indent should automatically adapt to instrument names' length. http://code.google.com/p/lilypond/issues/detail?id=766 This issue is now blocking issue 1015. See http://code.google.com/p/lilypond/issues/detail?id=1015 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1015 in lilypond: doc line width
Updates: Blockedon: 766 Comment #10 on issue 1015 by percival.music.ca: doc line width http://code.google.com/p/lilypond/issues/detail?id=1015 I think any "final solution" to this issue depends on the instrument-name issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 766 in lilypond: Indent should automatically adapt to instrument names' length.
Comment #4 on issue 766 by percival.music.ca: Indent should automatically adapt to instrument names' length. http://code.google.com/p/lilypond/issues/detail?id=766 hmm, google code lets me delete non-initial commments (I removed mine from comment 1, which was just saying "give a minimal example"), but not the initial report. (I wanted Valentin's nice example to be the first one) Here's an attached *PDF* showing the instrument name going off the left-hand side of the page. The generated png automatically shifts the entire thing to the right (like we'd like to happen for pdfs), so it doesn't show any problem. Attachments: foo.preview.pdf 17.8 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1093 in lilypond: automatic negative offset for instrument name positining
Updates: Status: Duplicate Mergedinto: 766 Comment #2 on issue 1093 by percival.music.ca: automatic negative offset for instrument name positining http://code.google.com/p/lilypond/issues/detail?id=1093 I think that Valentin's example in issue 766 is better than this one. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 766 in lilypond: Indent should automatically adapt to instrument names' length.
Comment #3 on issue 766 by percival.music.ca: Indent should automatically adapt to instrument names' length. http://code.google.com/p/lilypond/issues/detail?id=766 Issue 1093 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
