ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Frans Goddijn <frans@iaf.nl>, ntg-context@ntg.nl
Subject: Re: mpgraph.mp
Date: Thu, 07 Sep 2000 17:00:32 +0200	[thread overview]
Message-ID: <3.0.6.32.20000907170032.01a14aa0@pop.wxs.nl> (raw)
In-Reply-To: <20000907151705.B26393@cs.ucc.ie>

At 03:17 PM 9/7/00 +0100, Marc van Dongen wrote:
>Frans Goddijn (frans@iaf.nl) wrote:
>
>: There's a file called mpgraph.mp in the directory where I compile a .tex
file using texexec and now after every run of texexec, a
>: log text comes on screen saying it's metaposting mpgraph.mp and I must
enter a acommand at the * or type END.
>: 
>: I didn't have this before and I can't see how I got into this... When I
type END every time the respons comes on screen I seem to be
>: out of trouble but should I do something else to avoid this?
>
>Hi Frans,
>
>
>Do you need this file? If so, have you tried to remove
>or rename it? It is part of the standard mpost/(La)TeX
>distribution and perhaps you are using the wrong one
>(in the current directory).  For example, on my system
>it is in share/texmf/doc/metapost/base/mpgraph.mp in my
>TETEX directory.

The file involved is the file with runtime graphics that context generates
(mpgraph.mp and mprun.mp). When one adds \protectbufferstrue to the local
cont-sys.tex file, it's named jobname-mpgraph.mp. I wasn't aware of another
mpgraph file being aroun don the system. 

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
-------------------------------------------------------------------------


  parent reply	other threads:[~2000-09-07 15:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-07 14:07 mpgraph.mp Frans Goddijn
2000-09-07 14:17 ` mpgraph.mp Marc van Dongen
2000-09-07 14:26   ` mpgraph.mp Marc van Dongen
2000-09-07 15:00   ` Hans Hagen [this message]
2000-09-07 15:13     ` mpgraph.mp Marc van Dongen
2000-09-07 21:07       ` mpgraph.mp Hans Hagen
     [not found]         ` <877l8nj677.fsf@pf39.warszawa.sdi.tpnet.pl>
2000-09-08 15:04           ` mpgraph.mp Hans Hagen
2000-09-07 14:57 ` mpgraph.mp Hans Hagen
2000-09-07 15:19   ` mpgraph.mp Marc van Dongen
2000-09-07 16:21     ` mpgraph.mp Hans Hagen
2000-09-08 14:48   ` mpgraph.mp Slawek Zak
2000-09-08 15:28     ` mpgraph.mp Hans Hagen
2000-09-08 16:51       ` mpgraph.mp Slawek Zak
2000-09-09  0:18         ` mpgraph.mp Hans Hagen
2000-09-09  9:35           ` mpgraph.mp Frans Goddijn
2000-09-09 15:33             ` mpgraph.mp Slawek Zak
2000-09-09 16:53               ` mpgraph.mp Frans Goddijn
2000-09-11  7:17             ` mpgraph.mp Hans Hagen
2000-09-09 15:23           ` mpgraph.mp Slawek Zak
2000-09-09 17:17             ` mpgraph.mp Frans Goddijn
2000-09-11 14:56           ` mpgraph.mp Ed L Cashin
  -- strict thread matches above, loose matches on Subject: below --
2000-12-14 18:46 mpgraph.mp Frans Goddijn
     [not found] ` <20001214223321.A14378@ruhrau.de>
2000-12-16 14:06   ` mpgraph.mp Frans Goddijn
     [not found] <Hans Hagen's message of "Fri, 08 Sep 2000 17:28:26 +0200">

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.20000907170032.01a14aa0@pop.wxs.nl \
    --to=pragma@wxs.nl \
    --cc=frans@iaf.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).