On 1/12/2017 12:23 PM, Sergey Slyusarev wrote:

...

you can use \startMPinitializations \stopMPinitializations as these are expanded each graphic run

Thank you! This works fine with minimal example (in which the behaviour in question appears). But in specific context in which this problem affects me, this solution breaks many things:

There are many *MPinclusions with as many MPinstances (so variables from one instance don't contaminate another). (here's that place: https://github.com/jemmybutton/byrne-euclid/blob/master/preamble.tex#L30)

If this is indeed a bug and it's going to be fixed one day, I'll go with some less invasive hack to overcome it, but if this behaviour is correct, I'll try to rewrite everything accordingly.

the (subtle) difference between the two is not a bug but a feature

Or I got it wrong and *MPinitializations can substitute for *MPinclusions in this case?

yes

Sergey

___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________

-- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------