2012/12/2 David Kastrup <d...@gnu.org>: > Thomas Morley <thomasmorle...@googlemail.com> writes: > >> 2012/12/2 David Kastrup <d...@gnu.org>: >>> Thomas Morley <thomasmorle...@googlemail.com> writes: >>> >>>> How about adding >>>> \override Staff.KeyCancellation #'break-visibility = #'#(#f #f #f) >>>> to your score? >>>> Seems to work. >>> >>> I'd write ##(#f #f #f) instead. Vectors written as #(...) are already >>> constants (including quoting the contents). >> >> As far as I can tell, every example in the docs uses #'#( ... ) if a >> vector is given. > > Ugh. > >> Perhaps one should change this. > > I think one should. > >> OTOH, there's no harm using the additional '-sign. > > It implies that the quotation is needed, leading to surprises when you > try putting non-constant values in a vector and leaving off the '.
Sure. But this alone doesn't convince me. >> Thinking a little more about it, I would tend to keep the current behaviour: >> Remembering being a LilyPond-starter, the first time #'#(#f #f #f) >> occured to me, I couldn't see what was what under all the hash-signs >> and speculated, the # before the bracket was a typo. >> The '-sign gives a little structure to it, at least. > > But we don't write #'#f either. Why use an extra quote mark for one > autoquoting form and not for another? I didn't think about ##f. _That's_ convincing!! So I agree, we _should_ change the usage of #'#( ... ) -Harm _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
