Re: Issue 1336 in lilypond: skipTypesetting segfaults when set during a skipBars-induced MultiMeasureRest spanner

[David Kastrup]

address@hidden writes:

> Comment #11 on issue 1336 by v.villenave: skipTypesetting segfaults
> when set during a skipBars-induced MultiMeasureRest spanner
> http://code.google.com/p/lilypond/issues/detail?id=1336
>
> I may be completely wrong, but is there a particular reason why the
> MultiMeasureRest has to be printed as a Spanner *at all*? I mean, it's
> not  breakable,

It is material which changes its appearance depending on the chosen
breakpoints, since staffs can commit Harakiri in partituras and take the
multimeasure rest along with them.

It is also conceivable to allow several multimeasure rests be conflated
depending on horizontal spacing expediency, but I don't think that we
have something like that currently.

> it isn't really extended horizontally, it doesn't have a left or right
> bound...  Perhaps implementing it differently could also help us solve
> syntax inconsistencies such as r1\fermata vs R1-\fermataMarkup?

Not sure that the right solution to this problem lies here.

-- 
David Kastrup