Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities

[lilypond]

Comment #12 on issue 1555 by address@hidden: Multiple warnings  
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555

Perhaps we could minimize confusion by changing the terminology  
from "staff" and "nonstaff" to fixed and loose (loose, of course, is  
reflected in the code).  THen we could say that staves are, by default, set  
to be fixed, and lyrics, dynamics, chordnames, and fretboards are, by  
default, set to be loose.

Instead of staff-affinity, the property would become fixed-affinity.

The spacings would become things like

fixed-fixed-spacing
system-fixed-spacing
free-relatedfixed-spacing
free-unrelatedfixed-spacing

I admit that I am not totally enamored with this terminology.  But the  
current terminology implies there is some special quality about staves,  
rather than that there is a special quality about fixed lines.