Re: chord name collide with staff

[David Kastrup]

"address@hidden" <address@hidden> writes:

> On 4 févr. 2013, at 08:00, address@hidden wrote:
>
>> On 4 févr. 2013, at 01:00, MING TSANG <address@hidden> wrote:
>> 
>>> Hi fellow lily users:
>>> 
>>> I have a chord name and a melody staff.  The chord name collide
>>> with the melody staff on 2nd & 3rd systems in v2.17.11, but in
>>> v2.16.2 they are ok. Please refer to two pdf files and a lily text
>>> file.
>>> 
>>> Appreciate help to resolve this. 
>>>  
>>> Blessing in+,
>>> <my-god_test.ly>
>>> <my-god_test_v2-17-11.pdf>
>>> <my-god_test_v2-16-2.pdf>
>>> _______________________________________________
>>> lilypond-user mailing list
>>> address@hidden
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>> 
>> Yikes! It seems like the type of thing that I'd have caused and that
>> I could fix. Will keep you posted as of tomorrow with a solution.
>> 
>> Cheers,
>> MS
>
> Could this please be added to the tracker.
> Do people know if it is a regression?

>From the original report:

    I have a chord name and a melody staff. The chord name collide
    with the melody staff on 2nd & 3rd systems in v2.17.11, but in
    v2.16.2 they are ok. Please refer to two pdf files and a lily text
    file.

including two PDF files.

> I won't have time to git bisect until late tonight.  I'm assuming it
> was from the massive skyline push in August, but I'm not sure.

Well, instead of bisecting, I'd propose just checking the commits before
and after the skyline push.  If that does not introduce the regression,
bisection after that seems reasonable.

-- 
David Kastrup