Re: inconsistent \RemoveEmptyStaves action

[Lukas-Fabian Moser]

Hi Jay,

Am 12.02.22 um 20:22 schrieb jh:
> From one project to the next sometimes 'Frenching' a score works and 
> sometimes it doesn't
> This is the shortest example I could figure out how to make
> the second system should be just two staves (and using the same 
> context etc 5 days ago worked as expected on a different score so this 
> was copy pasted)

You are using PianoStaff. The only point of a PianoStaff is that it 
keeps all its contained staves alive together; to wit, the definition of 
PianoStaff is:

\context{
  \GrandStaff
  \name "PianoStaff"
  \alias "GrandStaff"

  \description "Just like @code{GrandStaff}, but the staves are only 
removed
together, never separately."

  \consists "Keep_alive_together_engraver"

  %% explicitly set instrument, so it is not inherited from the parent
  instrumentName = #'()
  shortInstrumentName = #'()
}

So the only difference between a PianoStaff and a GrandStaff is that, 
with a GrandStaff, you get what you want.

To be honest, it looks a bit strange to use a braced staff group for 
your score. Is this intentional?

(By the way, with current development versions of LilyPond, it suffices 
to issue \numericTimeSignature once - for example, in the \layout block. 
For \accidentalStyle ..., this has been true for a while now.)

Lukas