Re: What's with the spacing code?

[David Kastrup]

Joe Neeman <address@hidden> writes:

> On Thu, Sep 30, 2010 at 5:13 AM, David Kastrup <address@hidden> wrote:
>    
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>     \score { c }
>    
>     is indeed squeezed onto a single page even though it does not fit
>     at all
>     (it does not appear like any numbers of these scores will ever be
>     put on
>     two pages).
>
>
> How long has this been a problem? It comes from page breaks being
> forbidden all the way from the frontend, and I don't think that has
> been touched for a while...

Well, it is not desirable, anyway.  Between separate \score commands
should be a _good_ place to break.  When \score is intermixed with other
stuff, I would guess that _after_ a score would usually be a better
place than before it.

I have suspected Lilypond for a while to pick its page breaks in the
presence of multiple smallish \score commands somewhat disingenuously.

-- 
David Kastrup