Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning

[lilypond]

Updates:
	Summary: Concurrent slurs that start and end at the same moment should not  
produce a warning

Comment #10 on issue 1967 by address@hidden: Concurrent slurs that  
start and end at the same moment should not produce a warning
http://code.google.com/p/lilypond/issues/detail?id=1967

Ah, now that you point it out, I suppose that my implementation of that  
warning is to blame. In 2.12, no warning was printed at all if a second  
slur started while another slur was already active. I.e. the following  
snippet was not producing ANY warning in 2.12.3:

\version "2.12.3"
\relative c'' { c4( d( g g) }

I fixed this, but did apparently not consider the case that the second slur  
would start/end from within the same chord/moment (which is perfectly legal  
and should not produce a warning...).

So, a simpler test case for this bug is:

\version "2.12.3"
\new Voice \relative c'' { << { c( d) } { e( f) } >> }