On 2010/08/15 04:10:36, Carl wrote:
I tested, and verified that I don't need it, but why? I thought that
we had
checks to issue a warning if an undefined property was used. Is that
only for
context properties?
It depends on whether you think users are likely to do this (where you'd also have to `graphical' to an interface), \override TextScript #'graphical = ##t \override TextScript #'text = \markup \woodwind-diagram ... rather than this: \markup \override #'(graphical . #t) \woodwind-diagram ... There's no type-checking for markup props, but you can sneakily use them in grob overrides so they leak into markup, even if LilyPond protests. Cheers, Neil http://codereview.appspot.com/1946043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
