Re: looser spacing after 2.17.13

[David Kastrup]

Eluze <address@hidden> writes:

> David Kastrup wrote
>> Eluze &lt;
>
>> eluzew@
>
>> &gt; writes:
>> 
>>> Timothy Lanfear reports:
>>> http://lilypond.1069038.n5.nabble.com/Bad-vertical-spacing-with-instantiated-staves-td145151.html
>>>
>>> I couldn't find any hint why it changed with issues fixed with 2.17.14
>>>
>>> any clues?
>> 
>> There is one complex spacing change right after the following change,
>
> wow - that was quick!
>
> but: what is the 'following change'? following after what?
>
>> but the following one sounds like an even better candidate for the
>> problem:
>> 
>> commit d4802c72d26def39030f2ac897b66c3a268888d5
>> Author: Mike Solomon &lt;
>
>> mike@
>
>> &gt;
>> Date:   Tue Mar 5 20:59:20 2013 +0100
>> 
>>     Prevents chord names from being pushed into the staff (issue 3160)
>>     
>>     This is done by not removing empty skylines unless they are
>> suicidable.
>>     Proper space is thus reserved for these skylines in
>> align-interface.cc.
>
> so this is another following after…

The above commit is immediately succeeded by

commit 74e4d219b24ec6d6f28d663c0285418e6c8e122e
Author: Mike Solomon <address@hidden>
Date:   Tue Mar 5 21:03:55 2013 +0100

    Uses only unpure-pure containers to articulate unpure-pure relationships (is

[about a 100 lines of description elided]

-- 
David Kastrup