From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3054 Path: main.gmane.org!not-for-mail From: Marc van Dongen Newsgroups: gmane.comp.tex.context Subject: Re: texexec not launching mpost Date: Fri, 20 Oct 2000 20:09:04 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <20001020200904.Q24668@cs.ucc.ie> References: <3.0.6.32.20001020175956.01c881a0@pop.wxs.nl> <200010201856.UAA09361@bar.loria.fr> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035393815 13874 80.91.224.250 (23 Oct 2002 17:23:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:23:35 +0000 (UTC) Cc: NTG-ConTeXt Original-To: "Denis B. Roegel" In-Reply-To: <200010201856.UAA09361@bar.loria.fr>; from Denis.Roegel@loria.fr on Fri, Oct 20, 2000 at 08:56:55PM +0200 Xref: main.gmane.org gmane.comp.tex.context:3054 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3054 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. Regards, Marc van Dongen