From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: metafun manual
Date: Mon, 25 Sep 2000 23:56:17 +0200 [thread overview]
Message-ID: <3.0.6.32.20000925235617.017f5410@pop.wxs.nl> (raw)
In-Reply-To: <20000925182510.9922.qmail@crux.private.off-line>
At 08:25 PM 9/25/00 +0200, Joop Susan wrote:
>Ok. I only used 'fmtutil -all' after every ConTEXt/pdftex update. Better
>to use 'texexec'?
fmtutil does not handle mp mem files, probably because there are not so
many metapost formats
>> >Can you tell me why texexec cannot get this right in one run?
Context can if you enable runtime graphics : enable write 18 in texmf.cnf
and add the right switches to your local cont-sys.tex file (explained in
metafun manual).
>Is there any way of automatically detecting this situation.
very hard, but i'm thinking of one.
>Or does this mean that the only sure automated way to get a complete
>guaranteed up-to-date PDF file is to run:
>
>rm -f test1.tui test1.tuo test1.tmp test1.top
>rm -f mpgraph.[0-9]* mpgraph.mp mpgraph.log tmpgraph.* cont-opt.bak
>texexec --pdf test1
>mpost mpgraph.mp
>texexec --pdf test1
no, just enable run time generation, which is what I here, really: no
problems at all
>This is the brute force solution, possibly at the expence of extra
>processing time. Is this a bullet-proof final run?
as said, run time generated graphics are the best; fabrice popineau will
look into fast mpost launching in web2c, so that will speed up the process.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2000-09-25 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Mon, 25 Sep 2000 17:22:26 +0200." <3.0.6.32.20000925172226.00b755c0@pop.wxs.nl>
2000-09-25 18:25 ` Joop Susan
2000-09-25 21:56 ` Hans Hagen [this message]
2010-10-20 12:03 metafun Hans Hagen
2010-10-20 13:45 ` metafun manual Alan BRASLAU
[not found] <4133DD36@webmail.colostate.edu>
2004-08-31 8:00 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 16:42 Hans Hagen
2004-08-30 18:54 ` Willi Egger
2004-08-30 19:21 ` Re[2]: " Floris van Manen
2004-08-30 19:37 ` Brooks Moses
2004-08-31 2:25 ` Jojo
2004-08-31 8:25 ` Hans Hagen
2004-09-01 2:15 ` Jojo
2000-09-27 12:01 Joop Susan
[not found] <Your message of "Mon, 25 Sep 2000 10:46:55 +0200." <3.0.6.32.20000925104655.007c33a0@pop.wxs.nl>
2000-09-25 11:47 ` Joop Susan
2000-09-25 15:22 ` 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=3.0.6.32.20000925235617.017f5410@pop.wxs.nl \
--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).