Re: Issue 1311 in lilypond: New spacing code affects user-created pseudo-staff contexts

[lilypond]

Comment #5 on issue 1311 by address@hidden: New spacing code affects  
user-created pseudo-staff contexts
http://code.google.com/p/lilypond/issues/detail?id=1311

In the full example attached to this issue, the LyricStaff did nothing. It  
had no \accepts Lyrics, so 2.12 placed the Lyrics below the LyricStaff and  
then made LyricStaff silently disappear.  Hard to see how convert-ly could  
have helped in this case.

That example does produce a 'vertical spacing has changed' NOT_SMART  
message, due to the use of minimum-Y-extent to try to change staff-like  
spacing, but this was directed toward a ChordNames not the LyricStaff.   
That warning will help some users.

Would it be wise to suggest one consider staff-affinity wherever convert-ly  
sees \type "Engraver_Group"?  The only Engraver_Group defined in the .ly  
files at mutopiaproject.org is Dynamics, which is auto-converted.  Can  
anyone estimate whether such a message would cause more enlightenment than  
confusion?