From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3185
Path: main.gmane.org!not-for-mail
From: "Denis B. Roegel" <Denis.Roegel@loria.fr>
Newsgroups: gmane.comp.tex.context
Subject: suggestion
Date: Sat, 4 Nov 2000 00:06:23 +0100 (MET)
Sender: owner-ntg-context@let.uu.nl
Message-ID: <200011032306.AAA03340@bar.loria.fr>
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 1035393937 14932 80.91.224.250 (23 Oct 2002 17:25:37 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 17:25:37 +0000 (UTC)
Cc: roegel@lorraine.loria.fr (Denis B. Roegel)
Original-To: ntg-context@ntg.nl
Xref: main.gmane.org gmane.comp.tex.context:3185
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3185

Since errors in the tex or mpost runs often go unnoticed
when using texexec, wouldn't it be possible for texexec to
look for errors in the log files and report something
at the *end* of the final run?
I just got caught because I had written `: =' instead
of `:=' in some metapost code. texexec wouldn't show it.

Denis