ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Emil Hedevang Lohse <emil@imf.au.dk>
Subject: Extra run is needed for PDF output
Date: 19 Jul 2002 16:58:51 +0200	[thread overview]
Message-ID: <vg0it3bkbmc.fsf@durin.imf.au.dk> (raw)

Hello, 

In order to reflect changes in \start/\stopuseMPgraphic I somehow need
to run texexec twice when generating PDF output.

Specifically, I have a file named fun.tex containing

\setupcolors[state=start]
\starttext
Hello, World!
\startuseMPgraphic{a}
  fill fullcircle scaled 2cm withcolor green;
\stopuseMPgraphic
\useMPgraphic{a}
\stoptext

To make a PDF file I run 'texexec --pdf fun' and I do indeed get the
correct result. However, if I replace "green" with "red" I need to run
'texexec --pdf fun' twice to make the ball change color in the PDF
file. The file mpgraph.mp is updated after the first run and does
contain "red" instead of "green", and when I view mpgraph.1 there
surely is a red ball, but somehow a second run is needed for the
graphic to be included in the PDF file.

When I generate PS files with 'texexec fun && dvips fun' only one run
is needed. I expect this is because dvips includes the updated
mpgraph.1 file into the fun.ps file.

Is there some way I can get texexec to include the graphic without
running it twice? (I can, of course, just run 'texexec --pdf fun &&
texexec --pdf fun' but that seems to be overkill.)

I admit that I have not read the whole documentation, I am just a
ConTeXt-beginner. If the information is of any help, I am running the
full installation of TeXLive 7 under Debian GNU/Linux 3.0 on the x86
platform.

-- 
Emil Hedevang Lohse <http://home.imf.au.dk/emil/> 

Alle spørgsmål er lige dumme. 
Og spørgsmålet "Kan ænder flyve?" er ikke dumt.


             reply	other threads:[~2002-07-19 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19 14:58 Emil Hedevang Lohse [this message]
2002-07-19 20:21 ` 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=vg0it3bkbmc.fsf@durin.imf.au.dk \
    --to=emil@imf.au.dk \
    /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).