Am Montag, 22. März 2010 19:50:47 schrieben Sie:
> On 22/03/10 14:56, Reinhold Kainhofer wrote:
> > Am Dienstag, 16. März 2010 18:04:37 schrieb Reinhold Kainhofer:
> > 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, that's not what I'm doint.
That's exactly what xxx=\context{..} does now. And by storing the whole
context, it will later on reset the whole context to the settings when the
assignment was done (in particular the \RemoveEmptyStaff context saves the
status of the \Staff context during lilypond's initialization and later on
simply applies all these settings, reverting later manual changes to \Staff...
My patch only stores a list of context modifications, without a particular
context attached. Think of it as storing just the contents of a \with block.
E.g.
xxx = \with {
\remove Clef_engraver
\consists Ambitus_engraver
}
> I've seen later replies and I don't like "\with" in this usage (I nearly
> wrote "context").
>
> 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".
> <somecontext> \with {blah...}
> {....}
> is OK because the \with clause contains property values parameterizing
> the main context block.
That reasoning was also my motivation to not reuse \with, but add a new
keyword (although \with also works in this situation and is treated in the
parser just like the \contextmodifications keyword).
Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
