From xemacs-m  Wed Jul  9 19:02:02 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 TAA22045
	for <xemacs-beta@xemacs.org>; Wed, 9 Jul 1997 19:02:01 -0500 (CDT)
Received: (from hniksic@localhost)
	by jagor.srce.hr (8.8.6/8.8.6) id CAA01862;
	Thu, 10 Jul 1997 02:02:02 +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>
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 02:02:01 +0200
In-Reply-To: Steven L Baur's message of "09 Jul 1997 16:29:21 -0700"
Message-ID: <kig67ujepvq.fsf@jagor.srce.hr>
Lines: 50
X-Mailer: Gnus v5.4.59/XEmacs 20.3(beta12) - "Helsinki"

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

> I have noticed that MIME inline messages with x-uue encoding (like
> Michael Harnois' cartoon) beep and don't display properly.

What does "don't display properly" mean?  Do you get something like
"Peculiar error..."?  What does this print:

(signal 'buffer-read-only (list (current-buffer)))

And this:

(error-message-string (cons 'buffer-read-only (list (current-buffer))))

How about this:

(display-error (cons 'buffer-read-only (list (current-buffer)))
               (current-buffer))


For me, #1 beeps and prints "Buffer is read-only: #<buffer ...>" to
the minibuffer.  #2 evaluates to the same string, and #3 inserts it to
current buffer.

The same results are gotten with the old function.

> Doing (setq debug-on-error t) does not stop and give a lisp
> backtrace,

This is because `buffer-read-only' is a member of `debug-ignored-errors'.
And it's intentional (it's in 19.34, too), since it is really annoying
to get a debugger on every buffer-read-only error.  If the MIME code
wants to throw an error, it can use another code.

> but (setq debug-on-signal t) does.  If this is intended to be a
> feature, we should certainly add `Debug On Signal' to the Lisp
> interaction mode menu, and probably to the Options -> General
> Options menu as well.

No, definitely not.  `debug-on-signal' is a feature that should be
used *only* by people who know *very* well what they are doing.

To debug such errors, either set `stack-trace-on-signal' to t, or
remove the error in question from `debug-ignored-errors'.  I don't
recommend either of these actions to become the default.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Psychos _do not_ explode when sunlight hits them."

