ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Eckhart Guthöhrlein" <eckhart_guthoehrlein@public.uni-hamburg.de>
Cc: Hans Hagen <pragma@wxs.nl>, ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: problem with texexec and inline metapost
Date: Sat, 14 Jul 2001 12:38:43 +0200	[thread overview]
Message-ID: <5.1.0.14.0.20010714123334.00a8a840@public.uni-hamburg.de> (raw)
In-Reply-To: <3B502074.E1655240@quicknet.nl>

At 12:35 14.07.2001 +0200, Taco Hoekwater wrote:
> > >What latest? The ones i uploaded the last few days *do* an extra pass with
> > >external mp graphics {based on checksum calculation] but only with the
> > >undocumented --automprun, so
> > >
> > >texexec --automprun yourfile.tex
> >
> > Runtime graphics with \write18 are compiled each tex run, no matter if they
> > were changed or not. A checksum calculation could speed up things
> > significantly. Perhaps this is a feature worth thinking of, if it can be
> > implemented with acceptable effort.
>
>You need checksum calculation in TeX macros then, since nothing else is
>called
>inbetween. Possible, of course, but it might actually be slower than
>calling MP
>regardless of change.

But what about having texexec/perl calculate the checksums, writing them to 
an auxiliary file, and tex just reading them? And in any case, one can be 
sure that the mp code will not change during the same call to texexec (or 
can there be exceptions?), so that if, say, three tex runs are necessary, 
one run of mp would be sufficient. Setting some switch may be sufficient to 
achieve this.

Eckhart


  reply	other threads:[~2001-07-14 10:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 18:01 Eckhart Guthöhrlein
2001-07-04  6:47 ` Hans Hagen
2001-07-04  7:30   ` Eckhart Guthöhrlein
2001-07-14 10:02   ` Eckhart Guthöhrlein
2001-07-14 10:35     ` Taco Hoekwater
2001-07-14 10:38       ` Eckhart Guthöhrlein [this message]
2001-07-14 10:57         ` Taco Hoekwater
2001-07-16  7:33         ` Hans Hagen
2001-07-14 16:27 Eckhart Guthöhrlein
2001-07-16  7:36 ` 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=5.1.0.14.0.20010714123334.00a8a840@public.uni-hamburg.de \
    --to=eckhart_guthoehrlein@public.uni-hamburg.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).