Reinhold Kainhofer <reinh...@kainhofer.com> writes:
> 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?
Can't you just use
whatever = \with { \remove "Some_engraver" }
for those objects?
It would seem that this syntax is not yet taken.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
