From: Patrick Gundlach <patrick@gundla.ch>
Cc: patrick@gundla.ch
Subject: metapost not invoked? mpgraph.1 not created
Date: Sat, 17 Feb 2001 16:24:26 +0100 [thread overview]
Message-ID: <01021716242601.00407@levana> (raw)
Hi,
I use the following line to generate my pdf file:
texexec --pdf rahmen.tex
I have enabled write18 feature. I have put the following lines in
rahmen.tex:
\setupcolors[state=start]
\runMPgraphicstrue
\runMPTEXgraphicstrue
\useMETAFUNformattrue
\startuseMPgraphic{Kreis}
fill fullcircle scaled 200pt withcolor .625yellow ;
\stopuseMPgraphic
\useMPgraphic{Kreis}
\stoptext
\endinput
everything is just fine. After the texexec run, the pdf file includes the
circle.
But when I have the follwoing tex file:
\setupcolors[state=start]
\runMPgraphicstrue
\runMPTEXgraphicstrue
\useMETAFUNformattrue
\starttext
\startuseMPgraphic{Text}
draw btex \framed[width=fit,align=middle]{\input tufte \relax} etex ;
for i within currentpicture :
draw boundingbox i withpen pencircle scaled .2pt withcolor .625yellow ;
endfor ;
\stopuseMPgraphic
\useMPgraphic{Text}
\stoptext
\endinput
the mpgraph.1 will not be generated. (And an error appears in the pdf file
"file mpgraph.1 unknown"). The mpgraph.log tells me:
This is MetaPost, Version 0.641 (Web2C 7.3.1) (mem=metafun 2001.2.17) 17
FEB 2001 12:42
**&metafun mpgraph
(mpgraph.mp )
when I run 'mpost' and answer '&metafun mpgraph' when mpost outputs the two
**, the log looks like this:
This is MetaPost, Version 0.641 (Web2C 7.3.1) (mem=metafun 2001.2.17) 17
FEB 2001 12:42
**&metafun mpgraph
(mpgraph.mp
{randomseed:=2151}
write0 = `mpgraph.mpo'.
[1] )
1 output file written: mpgraph.1
then the next texexec run (exactly as above) looks correct to me.
Why does texexec (?) not create the mpgraph.1 ?
btw: TeXExec 2.5, pdfeTeX, Version 3.14159-13d-2.1, ConTeXt ver: 2001.1.9
--
Viele Grüße,
Patrick Gundlach
next reply other threads:[~2001-02-17 15:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 15:24 Patrick Gundlach [this message]
2001-02-19 10:47 ` Hans Hagen
[not found] <Your message of "Mon, 19 Feb 2001 11:47:49 +0100." <3.0.6.32.20010219114749.017fb4d0@server-1>
2001-02-19 12:57 ` Patrick Gundlach
2001-02-19 14:59 ` Hans Hagen
2001-02-21 2:16 ` Uwe Koloska
[not found] <Your message of "Mon, 19 Feb 2001 15:59:52 +0100." <3.0.6.32.20010219155952.019f7180@server-1>
2001-02-19 15:47 ` Patrick Gundlach
2001-02-19 16:22 ` Hans Hagen
[not found] <Your message of "Mon, 19 Feb 2001 17:22:59 +0100." <3.0.6.32.20010219172259.0157a600@server-1>
2001-02-20 10:48 ` Patrick Gundlach
2001-02-20 11:53 ` Hans Hagen
2001-02-20 15:42 ` Ed L Cashin
2001-02-20 15:58 ` Marc van Dongen
2001-02-20 16:40 ` Hans Hagen
2001-03-15 11:10 ` Slawek Zak
2001-03-15 11:14 ` Slawek Zak
2001-03-15 12:41 ` Patrick Gundlach
2001-03-15 19:45 ` Ed L Cashin
2001-02-20 21:22 ` Ed L Cashin
2001-02-21 12:51 ` Marc van Dongen
2001-02-21 16:53 ` Ed L Cashin
2001-02-21 17:17 ` Marc van Dongen
2001-02-21 17:22 ` Marc van Dongen
2001-02-21 2:08 ` Uwe Koloska
2001-02-20 14:13 Patrick Gundlach
[not found] <Your message of "Tue, 20 Feb 2001 12:53:44 +0100." <3.0.6.32.20010220125344.01cc87b0@server-1>
2001-02-20 14:16 ` Patrick Gundlach
2001-02-20 16:46 ` Hans Hagen
2001-02-20 21:35 ` Ed L Cashin
2001-02-22 15:39 Patrick Gundlach
2001-02-22 15:55 Patrick Gundlach
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=01021716242601.00407@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).