Re: [PATCH]: Allow context modifications to be stored in a variable and inserted into \context or \with

[David Kastrup]

Ian Hulin <address@hidden> writes:

> On 22/03/10 14:56, Reinhold Kainhofer wrote:
>> Am Dienstag, 16. März 2010 18:04:37 schrieb Reinhold Kainhofer:
>>> Am Freitag, 12. März 2010 14:41:20 schrieb Reinhold Kainhofer:
>>>> Our problems with \RemoveEmptyStaffContext resetting previous context
>>>> modifications highlights one problem we have: So far, it was not possible
>>>> to store a bunch of context modifications into a variable and apply them
>>>> later on.
>>>
>>> An updated patch is now available at
>>>      http://codereview.appspot.com/475041
>>
>> Before I finally push this (I assume the silence means approval ;-) ), I just
>> want to bring up the issue how to name the new command to store context
>> modifications.
>>
>> Initially I used \contextModifications {...}, but as Neil points out, all
>> parser keywords are supposed to be lowercase, so now we have the ugly-looking
>> \contextmodifications {...}...
>>
>> What do you think of this name, it is okay or too long/unclear?
>>
> Both.  How above xxx = \savecontext {...} (which is what your doing)?

No, it isn't.  That's the whole point.

> By and large \ commands tend to be verbs or nouns, and I don't know
> how to "with" anything, and I've never ever set eyes on a "with".

It is setting a variable to material to be used in a \with clause, just
like

varname = \chordmode { ... }

os setting a variable to material to be used in \chordmode clauses or
equivalent.

-- 
David Kastrup