Issue 546 in lilypond: Incorrect merging when a same note has different accidentals

[codesite-noreply]

Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546

Comment #1 by gpermus:
- it's not High.  High is for things like segfaults.  Unless you see 
otherwise in the
regtests, it's not even a regression.

- What is the (singular) bug here -- is it the accidental collision, or 
the merged
noteheads?  (hint: you can certainly file two bug reports for a single 
email; IIRC, I
once filed 4 issues based on a single email)

- where's the \version string?

- where's the attached png showing the problem?  lilypond -dpreview 
foo.ly   produces
the best output.

- I wouldn't say this is a nitpick; it looks fairly serious.  Nitpick 
is intended for
things like "the shape of this slur is kind-of ugly, although it 
doesn't collide with
anything"



Issue attribute updates:
        Labels: -Type-Collision -Priority-High -Engraving-nitpick Type-Defect 
Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings