Re: Context.Grob considered as symbol list

[Werner LEMBERG]

> One: response to the on-list posting of the patches, intended to be
> more useful for per-patch review, has resulted in zero followups.

Well I've already checked your changes on Rietveld, so I simply
skipped the patches sent to lilypond-devel.

> \tweak has an optional grob argument (now a string) situated before
> its target symbol.  This obviously won't survive upon converting the
> second argument to string as well.  What this means is that
>
>   \tweak Accidental #'color #red cis
>
> will have to get converted to
>
>   \tweak Accidental.color #red cis
>
> in order to preserve the optional character of Accidental.
> Contrasting this with
>
>   \override Accidental color #red or
>   \override Voice.Accidental color #red

Would it be possible to have

  \override Accidental.color #red
  \override Voice.Accidental.color

?  For me, this feels most natural.  In case a convert-ly rule is
feasible, I don't mind changing the syntax.


     Werner