[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5519 Give NoteNames context an \alias Staff

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Oh wow. The regtest does

<<

  \new NoteNames {
    \set printOctaveNames = ##f
    \voicea
  }
  \context Staff << 
    \accidentalStyle modern-voice-cautionary
    \new Voice \voicea
    \new Voice \voiceb
  >>
  \new NoteNames {
    \set printOctaveNames = ##f
    \voiceb

  }
>>

and now \context Staff no longer creates a Staff of its own (after all, NoteNames already provides one) so each \new Voice has to create its own Staff.

I'd call this regtest to be at fault here. I guess I'll just use \new Staff here.

---

[issues:#5519] Give NoteNames context an \alias Staff

Status: Started
Created: Fri May 17, 2019 12:10 PM UTC by David Kastrup
Last Updated: Fri May 17, 2019 08:03 PM UTC
Owner: David Kastrup
Attachments:

• 2019-05-17 21-02-58.png (63.4 kB; image/png)

Give NoteNames context an \alias Staff

This copies what issue 4452 did for the ChordNames context, avoiding
Staff-level property changes (like those issued by \key and
\transposition) to end up in unrelated contexts.

http://codereview.appspot.com/544700043

---

Sent from sourceforge.net because testlilyissues-auto@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto