Re: Context.Grob considered as symbol list

[Werner LEMBERG]

> [...]  I still don't want to make the interpretation of identifiers
> depend on case other than, of course, that you need to stick with
> the exact spelling of an identifier once you picked its name.

Besides limiting the namespace of user variables, what are your
arguments against such a change?  For me, the simplicity of being able
to always use `.' to mark the hierarchy instead of using a combination
of `<space>' and `.' definitely outweighs the namespace limitation.

> Werner picked up on something I mentioned as a dissatisfactory
> workaround idea, so there is little surprise that I am not in favor.
> I found a quite more satisfactory solution [...]

It seems that I'm missing something.  Let's assume that your footnote
syntax change is applied.  How do you then solve the case

  \tweak Accidental.color #red cis

vs.

  \override Voice.Accidental color #red

?


    Werner