Bug in drum chords

[Stef Epardaud]

Hello,

When you try the new syntax for chords on drum partitions, the result is
very weird. Attached is a test case (main file is bug-drums.ly) that
will try to play two toms at the same time, first with the <<>>
notation, then with the <> notation, then both toms one after the other.

As you can see the two results differ: indepedantly the pitches for the
toms are correct, as are the pitches for the <<>> notation, but the
pitches for the <> notation is completely different from those. Is it
normal ?

A non-related question is how exactly do we redefine drum-pitch-names
nowadays, since there seems to be a way to set a drum-kit (set-drum-kit)
but no way to define the new elements/pitches that we add to the drum
kit via drum-pitch-names ?
Specifically in the legend of the partition, you will see the 'stax' and
'sp' elements on the same pitch, but they should not, and lilypond
complains about this when running:
Parsing...#<Pitch a' >warning: lily-guile:  unknown drumpitch.
#<Pitch g' >warning: lily-guile:  unknown drumpitch.

This is related to not being able to do 
#(define-public drum-pitch-names (append `(
  (maxstax   stax     ,(ly:make-pitch 0 4 NATURAL ))
  (crash     cc       ,(ly:make-pitch 0 6 NATURAL ))
  (splash    sp       ,(ly:make-pitch 0 5 NATURAL ))
) drum-pitch-names ))

in drums.ly, because if I change it directly in
share/lilypond/2.1.8/scm/drums.ly it works correctly.


I'm using latest CVS by the way, thanks for any help.
-- 
Stéphane Epardaud