Re: Issue 471 in lilypond: explicitKeySignatureVisibility shouldn't be necessary here

[lilypond]

Comment #3 on issue 471 by address@hidden:  
explicitKeySignatureVisibility shouldn't be necessary here
http://code.google.com/p/lilypond/issues/detail?id=471

The problem is the second staff, which starts right after the line break.  
This means that the key signature setting for the lower staff happens  
before the third measure, i.e. at a line break. Thus lilypond creates a key  
signature at the end of the line and at the beginning of the new line. The  
staff in the first system will be killed, however, but the key signature  
grob already had its effect on horizontal spacing.