Thomas Morley <thomasmorle...@gmail.com> writes:
> Am Di., 14. Mai 2019 um 11:15 Uhr schrieb David Kastrup <d...@gnu.org>:
>>
>> Thomas Morley <thomasmorle...@gmail.com> writes:
>>
>> > Hi,
>> >
>> > consider the following snippet:
>> >
>> > musI = { \clef soprano e'4 }
>> > musII = { \clef alto c'4 }
>> >
>> > <<
>> > \new Staff \musI
>> > \new Staff \musII
>> > \new NoteNames \musII
>> >>>
>> >
>> > As long as the NoteNames-context is not commented/deleted the first
>> > unrelated Staff changes it's clef.
>>
>> The NoteNames context does not belong to a Staff. \clef effectively
>> contains a \context Staff setting which is consequently picked up by the
>> next Staff in its vicinity.
>>
>> Should NoteNames be aliased to Staff in order to pick up (and usually
>> ignore) this kind of setting?
>>
>> Possibly. It does have an Axis_group_engraver so it is Staff-like in
>> several ways.
>
> I'd vote for it. Can't see any disadvantage.
> Probably one would need to have a closer look at spacing-settings of
> VerticalAxisGroup, though, eventually they need to be modified.
> I'll give it a try as soon I can spare some time.
Seems unrelated to the issue at hand, though.
> For now a workaround is:
>
> \layout {
> \context {
> \NoteNames
> \alias Staff
> }
> }
>
> This one doesn't work:
> \new NoteNames \with { \alias Staff } ...
> Is this expected?
Things changing the context hierarchy are not interpreted in \with .
There are a few others as well. Possibly helps to keep
checks/consistency valid.
> Btw, same happens for Lyrics, if I try to enter \clef there. Ofcourse
> I don't expect someone to do this other than by accident.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
