From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3058 Path: main.gmane.org!not-for-mail From: "Denis B. Roegel" Newsgroups: gmane.comp.tex.context Subject: Re: texexec not launching mpost Date: Sat, 21 Oct 2000 23:46:43 +0200 (MET DST) Sender: owner-ntg-context@let.uu.nl Message-ID: <200010212146.XAA13313@bar.loria.fr> References: <20001020200904.Q24668@cs.ucc.ie> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035393819 13894 80.91.224.250 (23 Oct 2002 17:23:39 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:23:39 +0000 (UTC) Cc: Denis.Roegel@loria.fr (Denis B. Roegel), ntg-context@ntg.nl (NTG-ConTeXt) Original-To: dongen@cs.ucc.ie (Marc van Dongen) In-Reply-To: <20001020200904.Q24668@cs.ucc.ie> from "Marc van Dongen" at Oct 20, 2000 08:09:04 PM Xref: main.gmane.org gmane.comp.tex.context:3058 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3058 `Marc van Dongen' wrote > > Denis B. Roegel (Denis.Roegel@loria.fr) wrote: > > [snip] > > : that's the problem, isn't it? How can I investigate if mpto > : is really called and trap it? > > I haven't followed the discuission, so excuse me if what > I write doesn't make sense. Trapping mpto or whatever > program doesn't seem to be too difficult. Simply rename it to > mpto_old, and create a new mpto which calls mpto_old. If you're using > unix you can use redirection to catch errors/output and append them > to a log file. I have now followed your suggestion and created a file mympto where I put #! /bin/sh echo 'This is my mpto' /usr/local/tex5/bin/mpto $* and in the file texexec.ini, I put set MpToTeXExecutable to mympto Then, mympto is indeed called (as can be shown if I rename mympto into mympto2), but it doesn't change my problem. I really don't think the problem is the line set MpToTeXExecutable ... It has something to do with mpto. But again, if I just call mpost directly it works. For some reason, the current directory used by mpost is different from the one it should be. How could I investigate this in more depth? Thanks, Denis