> > % . I get a lot of
> > %
> > % programming error: No beam posns (Continuing; cross thumbs)
> > %
> > % warnings. I wasn't able to make the example shorter; if I remove a
> > % bar, lilypond formats it within a single line (BTW, this yields an
> > % *extremely ugly* result because the spacing is squeezed to a
> > % minimum), and the error doesn't occur.
>
> * Can you send me a stack-trace of the programming_error() ?
How shall I do this? Do you mean running lilypond with gdb, putting a
break point at programming_error, then typing `bt all'?
> * I believe it is related to
>
> for (int i=0; i < broken_intos_.size (); i++)
> {
> SCM al = broken_intos_[i]->get_grob_property ("all-elements");
> al = uniquify_list (al);
> }
>
> in system.cc. Can you see if the problem goes away if you comment
> out the uniquify_list() call? I cannot duplicate the problem ; it
> might be related to memory layout.
I see that you've removed the uniquify_list call already. Indeed, my
example works with CVS 2004-01-16 22:37 MET.
Werner
_______________________________________________
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
