Simon Albrecht <simon.albre...@mail.de> writes: > On 22.01.2018 18:29, David Kastrup wrote: >> Well, uhm. Sounds like accepting TabStaff by default might be sensible >> to do? > > Why would anyone need a TabStaff within a ChoirStaff? That doesn’t > make sense and I’m sure the TabStaff should be above or below the > ChoirStaff, or if in an exceptional score one had to put a tabulature > instrument between choir groups for whatever reason, one should use > two ChoirStaffs, one above and one below.
ChoirStaff mostly means "StaffGroup but without vertically connected bar lines". Just like "PianoStaff" means "GrandStaff but with Keep_alive_together_engraver". "Choir" or "Piano" point to a common use case but by no means the only one. In addition, where is the point in triggering behavior that is neither error or warning but just obscure? -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
