From: Patrick Gundlach <patrick@gundla.ch>
Subject: :-))))) Solution? mpgraph.1 now generated and metapost invoked...
Date: Thu, 22 Feb 2001 22:34:44 +0100 [thread overview]
Message-ID: <01022222344400.00760@levana> (raw)
Yessssssssssssss!
I am getting closer to the solution (?) of my darn problem:
in meta-ini.tex, I have changed the definition of \initializeMPgraphics to:
\def\initializeMPgraphics{\relax}
it was
\def\initializeMPgraphics% \unlinkfile{\MPgraphicfile.mp} -> empty file
{%\ifx\bufferprefix\empty \else
\immediate\openout\MPwrite\MPgraphicfile.mp
\immediate\write\MPwrite{end.}%
\immediate\closeout\MPwrite
}%\fi}
now metapost is invoked and the graphic is correctly included in my pdf
file :-)))))))
The problem was that I always ended up with a file (mpgraph.mp) who's
content was just a simple
end.
and after the final run, the mpgrap.mp contained a sensible contents. But
that was not metaposted.
But I did not notice it at all, since texexec would not stop between the
the different runs of context/etc.
--
Viele Grüße,
Patrick Gundlach
next reply other threads:[~2001-02-22 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 21:34 Patrick Gundlach [this message]
2001-02-23 10:04 ` 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=01022222344400.00760@levana \
--to=patrick@gundla.ch \
/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).