Thomas Morley <thomasmorle...@googlemail.com> writes:
> this code used to work with 2.16.2:
>
> \version "2.16.2"
>
> \new Staff \with { \accepts "ChordNames" }
> \new ChordNames \chordmode { \override ChordName #'Y-offset = #-1 c }
Why would you want to have "ChordNames" internal to a Staff?
> With 2.17.12 an programming error occurs:
>
> GNU LilyPond 2.17.12
> Processing `atest-22.ly'
> Parsing...
> Interpreting music...
> programming error: duplicate axis group
> continuing, cross fingers
> Preprocessing graphical objects...
> programming error: vertical alignment called before line breaking
> continuing, cross fingers
> ...
>
> Seems it is caused by having replaced the (general deleted)
> "Hara_kiri_engraver" by "Axis_group_engraver" in /ly/engraver-init.ly:
> ChordNames.
I doubt it. Hara_kiri_engraver was a fully functional axis group
engraver. More likely the error message is new and was only introduced
because the skylines code caused multiple axis groups to explode.
> Well, I'm not sure this is a real bug, though, do we really intend
> this behaviour?
I think if we forcefully nest contexts supposed to contain their own
axis group, we need to deal with the consequences. It would likely be
better to do this automatically, presumably by dismissing the inner axis
group. However, I don't know whether this will not also break the
Hara_kiri functionality.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
