Re: Context.Grob considered as symbol list

[Keith OHara]

David Kastrup <dak <at> gnu.org> writes:

> \tweak Accidental.color #red cis

> \override Voice.Accidental color [=] #red

> This is a bit unsatisfactory[sic].  Basically, the optional component is
> separated by a period.  

This is just lovely.  Any optional components are consistently separated 
by periods.

> While that is reasonably understandable, the
> difference in syntax is a bit of a nuisance. 

\tweak and \override have always had different syntax
  \tweak property value item
  \override Grob property = value

> Also, \override syntax is
> backwards compatible, the grob-augmented \tweak syntax (granted, just
> available since 2.16) is not.

Maybe not backwards compatible, but convert-ly-able as shown nicely in 
your patch.

Can anyone reading here (other than David who implemented it) give an 
example where he has used the grob-augmented \tweak syntax ?