Re: Insane spring distance

[Jim Long]

On Sat, Feb 09, 2013 at 12:22:47AM -0800, Mark Stephen Mrotek wrote:
> The second example differs from the first example. It does not have a
> partial measure. 

But of course.  If it were the same, it wouldn't be a second
example, it would be the first example, repeated.  :)

The purpose of the second example was to test the hypothesis that
the warning produced by the first example was because I had
attached something (a markup) to an item that does not exist as a
drawn entity, and that I should not expect to be able to attach
markup to non-drawn entities.

But back to the first example, I mostly just wanted to point out
that LilyPond trapped this as a programming error.  But to Lily's
credit, the output seems to be rendered correctly.  Perhaps the
action that Lily is performing as a result of the programming
error in indeed the correct action, and should be taken
deliberately, rather than by default.  IOW, maybe it's not a
programming error -- the output appears to be correct.  And if a
warning is necessary, it could perhaps be better worded and/or
cite a line number.  It took me a few minutes to figure out what
was causing the programming error warning.

But again, it renders fine, so it's very low priority, as I
alluded to in the original post.

> My conclusion is that the error is caused by the spacer being the only
> object in the partial measure.

I concur, except to add that the \markup is key.  A spacer as the
only object in a partial measure is fine, unless you try to
attach markup to it.

Cheers,

Jim