Paul Scott wrote: > Yitz Gale wrote: >> The Chord Name engraver with chordChanges = #t >> does not print the chord at the beginning >> of a repeat alternative if the chord at the >> end of the previous repeat alternative was >> the same.
> The way I read the 2.6 documentation This bug is not specific to 2.6. It affects 2.8 and 2.9 also (I think). > ...you want to set chordChanges = ##f if you > want the chord printing to change when you want > it to instead of when the chord changes. > Is that what you meant? No. I want the chords to print when they change. For this, I need to set chordChanges = ##t. However, there is a bug that causes lilypond to skip a chord in a certain case even though it is a change, as described above, and as shown in my example. _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
