#4807 Wrong glissando slopes with accidental in target chord

[Simon Albrecht]

As Harm reported, glissando slopes may be wrongly calculated, if there is an accidental on the target chord. This worked fine in v2.16.2.

\version "2.18.2"
%% up to 2.19.39

{ <d f>1\glissando <fis'' a''>1 }

%% this one is ok:
{ <d f>1\glissando <f'' a''>1 }

[David Kastrup]

The responsible commit is
b47350d1efb1128b2a8ea13f340dd5e3a53f0735 is the first bad commit
commit b47350d1efb1128b2a8ea13f340dd5e3a53f0735
Author: Keith OHara k-ohara5a5a@oco.net
Date: Sat Aug 24 14:06:57 2013 -0700

Draw glissando to accidental, not accidental_placement; issue 40

:040000 040000 6d0810fb614f48d24011889d305bdc62782aee7f 593b92fc536ba2491ab749d937fefa70c6344b29 M lily

This was committed in version 2.17.25

I'd have marked Keith as the owner (for apparent lack of a CC option in the tracker, expecting him to disown the issue if he is not seeing fit to look at it) but it appears like he's not in the SourceForge user base anyway.