ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mr. Wang Lei" <lwang@amath8.amt.ac.cn>
Cc: NTG-ConTeXt <ntg-context@ntg.nl>
Subject: Re: texexec not launching mpost
Date: Thu, 19 Oct 2000 11:21:33 +0800 (CST)	[thread overview]
Message-ID: <Pine.GSO.4.21.0010191059560.9064-100000@AMath13> (raw)
In-Reply-To: <200010182118.XAA07118@bar.loria.fr>

On Wed, 18 Oct 2000, Denis B. Roegel wrote:

> When I run texexec on the file below, the mpgraph.mp file
> is created, but not metaposted. I can call texexec as many
> times as I want, it doesn't help. I have to call mpost 
> by hand and then it works. I have shell_escape = 1 if

                      it should be "shell_escape = t"

You need set other environment as suggestted by hans
in metafun manual. you can see if you have set the following
in your cont-sys.tex:

   \runMPgraphicstrue 
\runMPTEXgraphicstrue
  \recycleMPslotstrue 
\useMETAFUNformattrue

You'd better set metapost command using texexec in you
texmf.cnf:

MPXCOMMAND = texexec --mptex
TEX = texexec --once --batch --nomp

You may need edit the texexec.ini, too. comment the
corresponding line which set the MpToTeXExecutable
to mptotex. for example, if you use tetex, comment
the line:

for  tetex  set  MpToTeXExecutable to  mptotex 

Hans, I have not find the excutable command named 
"mptotex" both in tetex and fptex. They only have 
"mpto". Another problem is that if I set the output
default is pdftex in my cont-usr.tex, texexec will
give a "can not found tmpgraphic.1" message if I
use \btex ... \etex in the metapost figure. because 
the part in \btex ... \etex will be processed by
texexec and give a pdf output, so there is no dvi
and can not generate tmpgraphic.1 which needed by
mptopdf.  

Wang

------------------------------------------------------------------------
Mr. Wang Lei                      Phone: 86-10-62541687 
Institute of Applied Mathematics  Email: lwang@amath8.amt.ac.cn
Chinese Academy of Science        Address: P.O.Box 2734, Beijing, 100080  
------------------------------------------------------------------------                                                 


  reply	other threads:[~2000-10-19  3:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-18 21:18 Denis B. Roegel
2000-10-19  3:21 ` Mr. Wang Lei [this message]
2000-10-19  9:04   ` Hans Hagen
2000-10-19 11:41     ` Mr. Wang Lei
2000-10-19 13:01   ` Denis B. Roegel
2000-10-19 13:45     ` Hans Hagen
2000-10-19 19:17       ` Denis B. Roegel
2000-10-19 19:30         ` Denis B. Roegel
2000-10-20  2:34           ` Mr. Wang Lei
2000-10-20 14:13             ` Denis B. Roegel
2000-10-20 15:59               ` Hans Hagen
2000-10-20 18:56                 ` Denis B. Roegel
2000-10-20 19:09                   ` Marc van Dongen
2000-10-21 21:46                     ` Denis B. Roegel
2000-10-22 18:49                       ` Hans Hagen
2000-10-22 18:30                   ` Hans Hagen
2000-10-23 19:34                     ` Denis B. Roegel
2000-10-24  6:48                       ` Hans Hagen
2000-10-20 17:36               ` Mr. Lei Wang
     [not found] <3.0.6.32.20001027113959.0154f7a0@pop.wxs.nl>
     [not found] ` <200010271431.QAA03427@bar.loria.fr>
2000-10-27 15:55   ` 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=Pine.GSO.4.21.0010191059560.9064-100000@AMath13 \
    --to=lwang@amath8.amt.ac.cn \
    --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).