Heh. Unrelated, but interesting.
Looking at the ChordPro documentation again, I thought I'd try putting multiple {key} directives in a CP that's already in the MS database, since it starts in F and goes to G for the last verse. Looks like MS doesn't really handle multiple {key} directives; it just goes with the last one it sees in the file (the abrogation method). If I put {key: F} at the beginning, then insert {key: G} right before verse 3, MS says that the song is in G.
I can't think of a reason that this would really matter, or how MS should actually handle it (current behavior might be perfectly reasonable), it's just an observation.
Looking at the ChordPro documentation again, I thought I'd try putting multiple {key} directives in a CP that's already in the MS database, since it starts in F and goes to G for the last verse. Looks like MS doesn't really handle multiple {key} directives; it just goes with the last one it sees in the file (the abrogation method). If I put {key: F} at the beginning, then insert {key: G} right before verse 3, MS says that the song is in G.
I can't think of a reason that this would really matter, or how MS should actually handle it (current behavior might be perfectly reasonable), it's just an observation.