https://codereview.appspot.com/110060045/diff/1/Documentation/extending/programming-interface.itely
File Documentation/extending/programming-interface.itely (right):

https://codereview.appspot.com/110060045/diff/1/Documentation/extending/programming-interface.itely#newcode1339
Documentation/extending/programming-interface.itely:1339: @end lilypond
This passage is too long.  One thing that is worth mentioning is that
\applyContext tends to be a last resort.  When one quotes music or
otherwise manipulates or replays it, the actions taken by applyContext
are basically opaque.  \set/\override/\revert are turned into
corresponding stream events and one can simulate or interpret the
actions they are taking and knows which properties are affected.

\applyContext, in contrast, has arbitrary effects.  While it also can be
recorded and replayed as a stream event, there is no way of knowing its
effects on the context's properties without actually making the call and
comparing the context properties before and afterwards.  And its effects
will depend on the status of the current context, to boot.

https://codereview.appspot.com/110060045/

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to