ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: :-))))) Solution? mpgraph.1 now generated and metapost invoked...
Date: Fri, 23 Feb 2001 11:04:58 +0100	[thread overview]
Message-ID: <3.0.6.32.20010223110458.01bc8c30@server-1> (raw)
In-Reply-To: <01022222344400.00760@levana>

At 10:34 PM 2/22/01 +0100, Patrick Gundlach wrote:
>Yessssssssssssss!
>
>I am getting closer to the solution (?) of my darn problem:
>in meta-ini.tex, I have changed the definition of \initializeMPgraphics to:
>
>\def\initializeMPgraphics{\relax}
>
>it was
>
>\def\initializeMPgraphics% \unlinkfile{\MPgraphicfile.mp} -> empty file 
>  {%\ifx\bufferprefix\empty \else 
>     \immediate\openout\MPwrite\MPgraphicfile.mp
>     \immediate\write\MPwrite{end.}%
>     \immediate\closeout\MPwrite 
>   }%\fi}
>
>
>now metapost is invoked and the graphic is correctly included in my pdf 
>file :-)))))))

If you wanto to change that, add your patch to you cont-sys.tex file, not
to meta-ini, 

\let\initializeMPgraphics\empty 

>The problem was that I always ended up with a file (mpgraph.mp) who's 
>content was just a simple
>end.

This should not give problems. 

>and after the final run, the mpgrap.mp contained a sensible contents. But 
>that was not metaposted.
>But I did not notice it at all, since texexec would not stop between the 
>the different runs of context/etc.

I'm a bit puzzled. Texexec won't even process files that small. 

Hans
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      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
-------------------------------------------------------------------------


      reply	other threads:[~2001-02-23 10:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 21:34 Patrick Gundlach
2001-02-23 10:04 ` Hans Hagen [this message]

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.20010223110458.01bc8c30@server-1 \
    --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).