Re: Context.Grob considered as symbol list

[Reinhold Kainhofer]

On 2012-10-12 00:25, David Kastrup wrote:> \tweak gets one symbol list, 
\override gets two symbol lists.  The
> symbol list for \tweak may optionally start with a grob name, the first
> symbol list for \override may optionally start with a context name.  I
> can offer \tweak color.Accidental #red cis as the optional form for
> \tweak, but that seem bonkers.

Is there really no way to determine whether a symbol describes a 
context, a grob or a grob property?

We don't neccessarily need this at the parsing stage. We might change 
the internal functions to use a list to describe the full path for grob 
properties, and the functions that handle them could then check whether 
the first entry is a context, a grob or a property.

Cheers,
Reinhold

--
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://www.kainhofer.com
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * Edition Kainhofer, Music Publisher, http://www.edition-kainhofer.com