From: Alan Braslau <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug: \textext inside \*MPinclusions causes error
Date: Thu, 12 Jan 2017 09:53:26 -0700 [thread overview]
Message-ID: <20170112095326.1110dd7c@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <444c2452-8da7-22ce-5450-b596897ac174@wxs.nl>
On Thu, 12 Jan 2017 10:06:09 +0100
Hans Hagen <pragma@wxs.nl> wrote:
> you can use
>
> \startMPinitializations
> \stopMPinitializations
>
> as these are expanded each graphic run
>
> action pass 1 pass 2
>
> definitions yes
> extensions yes
> inclus figure yes
> initializations yes yes
> metapost code yes yes
> end figure yes yes
One needs to remember that MPlib goes through several runs, and many
standard MP code examples are written for a single, mpost run. This
means that code can fail if variables, for example, are not properly
initialized (or re-initialized). Another example is reading from files
in MP, as the file descriptors are kept open by default, reading on from
where one stopped in a previous run.
Alan
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-01-12 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 22:08 Sergey Slyusarev
2017-01-12 9:06 ` Hans Hagen
2017-01-12 16:53 ` Alan Braslau [this message]
2017-01-12 11:23 Sergey Slyusarev
2017-01-15 17:55 ` Hans Hagen
2017-01-16 19:31 Sergey Slyusarev
2017-01-17 8:35 ` Hans Hagen
2017-01-21 21:13 ` Sergey Slyusarev
2017-01-22 12:23 ` Hans Hagen
2017-02-13 22:36 ` Sergey Slyusarev
2017-02-14 12:13 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170112095326.1110dd7c@zoo.hsd1.co.comcast.net \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).