From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Overwritten metapost files
Date: Thu, 27 May 2004 22:48:30 +0200 [thread overview]
Message-ID: <6.0.1.1.2.20040527224643.01cb7d48@localhost> (raw)
In-Reply-To: <20040527154705.GA9328@puritan.pcp.ath.cx>
At 17:47 27/05/2004, you wrote:
>How was it one avoided getting metapost overwritten? I have two
>metapost graphics in a .tex file defined by \startreusableMPgraphic and
>the first one gets overwritten by the second when running
>
> texexec --path=.. masters-project.tex
i suppose that you have a good reason for doing that -) you may try:
\recycleMPslotsfalse
Hans
next prev parent reply other threads:[~2004-05-27 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 15:47 Nikolai Weibull
2004-05-27 20:48 ` Hans Hagen [this message]
2004-05-28 8:16 ` Nikolai Weibull
2004-05-28 19:27 ` Henning Hraban Ramm
2004-05-29 9:36 ` Nikolai Weibull
2004-05-29 9:47 ` Patrick Gundlach
2004-05-29 10:01 ` Nikolai Weibull
2004-05-29 10:11 ` Patrick Gundlach
2004-05-29 12:55 ` Maurice Diamantini
2004-06-01 18:45 ` 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=6.0.1.1.2.20040527224643.01cb7d48@localhost \
--to=pragma@wxs.nl \
--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).