From xemacs-m  Wed Jul  9 22:43:10 1997
Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id WAA25074
	for <xemacs-beta@xemacs.org>; Wed, 9 Jul 1997 22:43:09 -0500 (CDT)
Received: (from hniksic@localhost)
	by jagor.srce.hr (8.8.6/8.8.6) id FAA18272;
	Thu, 10 Jul 1997 05:43:09 +0200 (MET DST)
To: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Re: XEmacs 20.3-beta12 "Helsinki" is released
References: <m2en984tp2.fsf@altair.xemacs.org> <kigiuyjettf.fsf@jagor.srce.hr> <m2yb7fu7n2.fsf@altair.xemacs.org> <kig67ujepvq.fsf@jagor.srce.hr> <m2vi2ju4nh.fsf@altair.xemacs.org> <kigrad7d7s5.fsf@jagor.srce.hr> <m2lo3ftyp8.fsf@altair.xemacs.org>
X-Attribution: Hrv
X-Face: Mie8:rOV<\c/~z{s.X4A{!?vY7{drJ([U]0O=W/<W*SMo/Mv:58:*_y~ki>xDi&N7XG
        KV^$k0m3Oe/)'e%3=$PCR&3ITUXH,cK>]bci&<qQ>Ff%x_>1`T(+M2Gg/fgndU%k*ft
        [(7._6e0n-V%|%'[c|q:;}td$#INd+;?!-V=c8Pqf}3J
From: Hrvoje Niksic <hniksic@srce.hr>
Date: 10 Jul 1997 05:43:08 +0200
In-Reply-To: Steven L Baur's message of "09 Jul 1997 19:42:27 -0700"
Message-ID: <kigvi2ja7xv.fsf@jagor.srce.hr>
Lines: 34
X-Mailer: Gnus v5.4.59/XEmacs 20.3(beta12) - "Helsinki"

Steven L Baur <steve@xemacs.org> writes:

> > Well, this looks good to me.  Have I missed anything?
> 
> Yup.  Everything.  Here is what an inline MIME message is supposed to
> look like at the top:

I am still missing it.

When the image is decoded correctly, the "good" message is printed (as 
your second GIF shows).  When an error is signaled, the error is
printed (as your first GIF shows).

Or, do you want to say that the error was somehow mistakenly printed
by error-displaying code?  It would seem highly unlikely to me.

> If it means that much to you, come up with a simple procedure for
> describing how to guarantee a lisp backtrace to a naive user.  This is
> a huge loss on the support side.

That is what GNU Emacs has done for years, and I don't think it's such
a huge loss.  Many people have requested this feature explicitly,
including you, and I have implemented it correctly.

In 99% of the cases, the procedure to produce a Lisp backtrace
(because nothing *guarantees* it) is to set debug-on-error to t.  If
this fails for some obscure reason, we'll deal with it as a special
case, which it is.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Beware of bugs in the above code; I have only proved it correct,
not tried it."                                    -- Donald Knuth

