Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs

[lilypond]

Comment #21 on issue 2584 by address@hidden: please make partcombine merge  
slurs
http://code.google.com/p/lilypond/issues/detail?id=2584

Ok, here is the question: are people ok with the following behavior  
(independently for each spanner-id):
a) multiple slur starts on the same moment are not an error but the same as  
one.
b) multiple slur ends on the same moment are not an error but the same as  
one.
a2) there will be a slur with direction UP if there is at least one such  
start event, and there will be a slur with direction DOWN if there is at  
least one such end event.  This might imply a double slur, but for ending  
it, a single slur end is sufficient.

Consequently, a^(_( c)) (the second closing paren not required, just added  
for prettiness) will add a double slur.  \slurUp a(_( c)) would just  
produce a DOWN slur I guess, since the direction override of \slurUp does  
not affect the slur events but the slur grobs.

It would make tampering with the doubleSlurs property mostly uninteresting,  
and one would have the equivalent functionality available for phrasing  
slurs.

Sounds reasonable?