David Kastrup wrote
> Eluze <
> eluzew@
> > writes:
>
>> while looking for a solution for a problem on lilypond-user I naively
>> entered
>> the code
>>
>> \layout {
>> \context {
>> \GrandStaff \RemoveEmptyStaves
>> } }
>>
>> which blasted LilyPond!
>>
>> just a stupid user handling case or should LilyPond rather issue an
>> appropriate message?
>
> It does not "blast" anything here.
where are you then?
this obviously only happens when there is an explicit \GrandStaff involved -
here is a full - not compiling - example for Windows 7:
\new GrandStaff \new Staff { a }
\layout {
\context {
\GrandStaff
\RemoveEmptyStaves
}
}
\version "2.17.4"
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/RemoveEmptyStaves-in-a-GrandStaff-brings-LilyPond-to-crash-tp134470p134474.html
Sent from the Bugs mailing list archive at Nabble.com.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
