On Thursday, 18 May 2000, "James Hammons" writes:
> > 1.3.51
> > ======
> >
> > * Don't use regex in chord-names.scm under windows; hybrid chordnames
> > user+calculated will be partly broken.
>
> I was trying to fix up the chord appearance when I noticed this little
> blurb--does this mean that guile is broken in windows? The attached file
> shows some difficulties I've been having in getting lily to behave when
> using chords (this example is straight from /input/test/american-chords.ly).
> Notice that the C6/9 is being notated as Cmaj6maj7/9 and the Cmaj9 is being
That's the bug, with a bug-free guile (eg on Linux), you'd get
Cmaj6/maj7/9
'Cmaj6' is in the american user chord list, but without regex's lily
can't determine whether an extra separating '/' is needed.
> notated as Cmaj7/9... Is this due to a lack of regex being used, and if so,
> who do I need to bug about getting it fixed? ;-p
It seems, though, that you want to fix these names, and you may do that
in the american chord list (chord::names-alist-american) in
scm/chord-names.scm.
> BTW, the reason I haven't sent any corrections to the american chord parsing
> yet is that I haven't had much free time lately! Once I know the status of
> this little bug I can proceed...
Take your time.
Greetings,
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
