From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3062 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: texexec not launching mpost Date: Sun, 22 Oct 2000 20:30:23 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <3.0.6.32.20001022203023.008e3470@pop.wxs.nl> References: <3.0.6.32.20001020175956.01c881a0@pop.wxs.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: main.gmane.org 1035393822 13918 80.91.224.250 (23 Oct 2002 17:23:42 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:23:42 +0000 (UTC) Cc: Denis.Roegel@loria.fr (Denis B. Roegel), ntg-context@ntg.nl (NTG-ConTeXt) Original-To: "Denis B. Roegel" In-Reply-To: <200010201856.UAA09361@bar.loria.fr> Xref: main.gmane.org gmane.comp.tex.context:3062 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3062 At 08:56 PM 10/20/00 +0200, Denis B. Roegel wrote: >`Hans Hagen' wrote >> >> >Randomizer initialized to 1119063014. >> > TeXExec 2.2 - ConTeXt / PRAGMA ADE 1997-2000 Isn't version 2.3 in the beta zip? >> > >> > metapost to tex : mpgraph >> >sh: mptotex: not found >> >> Yes, so you have to set MpToTeXExecutable to mpto or comment the line >> mentioned in texexec.ini [maybe you should check your texexec.ini with >> texexec.rme] It really works when set up ok. > >I have done all of this, it doesn't work. Neither commenting the line, >nor removing it. > >What can I do now? > >Maybe if I understand exactly how it works I can try to debug? >texexec calls mpost, which should call mpto. No! MP does not call mpto etc. The reason for this is that (1) this process is too sensitive for problems and (2) some of those tools are sensitive for long lines and so (3) etc etc This is why texexec does the calls after some cleaning up and check. It also makes sure that it uses a temp file that does not clash. >This apparently works since there is no such error as above. >But what I do not understand is why the mpto run fails, because >that's the problem, isn't it? How can I investigate if mpto >is really called and trap it? You can look into texexec [search for doRunMP or ######] and add lines like print "IT WORKS TILL HERE\n" ; inside conditionals to check if you come that far. Also, say texexec --verbose to get an idea of what the settings are. Can be helpful. 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 -------------------------------------------------------------------------