Phil Holmes <email <at> philholmes.net> writes:
> In the NR, 5.1.7 Context layout order, LilyPond up to 2.17.9 used to produce
> the correct output. After 2.17.11 it failed, and output the following error
> messages:
>
We get the old behavior if we ask ChordNames to stop trying to be a separate
line
\context { \ChordNames \remove Axis_group_engraver }
and maybe LilyPond should figure that out on her own.
But also, this example was hard for me to understand. It was not obvious that
\chords creates a ChordNames context, nor what chords are supposed to look like
when they are 'accepted' by a Staff.
Maybe use an example with a grouping context like PianoStaff :
\score {
\new PianoStaff <<
\new Staff { d'1 b1 }
\new Lyrics \lyricmode {la la }
\new Staff {\clef bass R1*2} >>
\layout {
\context {
\PianoStaff
%% \denies "Lyrics"
} } }
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
