From xemacs-m  Sat Mar 22 19:25:10 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id TAA01861
	for <xemacs-beta@xemacs.org>; Sat, 22 Mar 1997 19:25:09 -0600 (CST)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.5/8.8.5) id RAA09691;
	Sat, 22 Mar 1997 17:36:45 -0800
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: odd gnus error
References: <87rah7pn4m.fsf@sbt.net>
X-Url: http://www.miranova.com/%7Esteve/
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: Michael Harnois's message of 22 Mar 1997 16:39:17 -0600
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: 22 Mar 1997 17:36:41 -0800
Message-ID: <m2iv2j8k46.fsf@altair.xemacs.org>
Lines: 60
X-Mailer: Gnus v5.4.34/XEmacs 20.1(beta10)

Michael Harnois writes:

> I don't know if this is XEmacs or gnus. For a week or so, occasionally
> when entering a newsgroup, I get the error

> Signaling: (end-of-buffer)
>   gnus-set-summary-default-charset()

It's possible you're getten bitten by the (forward-char) in that
function.  The interface to forward/backward-char, scroll-up/down,
next/previous-line was integrated.  In 19.14 sometimes they beeped on
buffer boundaries and sometimes they didn't.  Now that behavior is
controlled by a variable called `signal-error-on-buffer-boundary'
It's been this way since about 19.15-beta4 or beta5.

From the looks of it, if you ever end up with a buffer that lacks a
trailing newline at the end of the buffer you will lose.


C-h f forward-char
forward-char: (&optional ARG BUFFER)
  -- an interactive built-in function.
Move point right ARG characters (left if ARG negative).
On reaching end of buffer, stop and signal error.
Error signaling is suppressed if `signal-error-on-buffer-boundary'
is nil.  If BUFFER is nil, the current buffer is assumed.


I think the signaling aspect of the movement functions is broken, but
it's rather too late change to it.

Try this patch to gnus-sum-mime.el and see if it helps.

Index: lisp/tm/gnus-sum-mime.el
===================================================================
RCS file: /usr/local/xemacs/xemacs-20.0/lisp/tm/gnus-sum-mime.el,v
retrieving revision 1.4
diff -u -r1.4 gnus-sum-mime.el
--- gnus-sum-mime.el	1997/03/16 03:05:46	1.4
+++ gnus-sum-mime.el	1997/03/23 01:33:35
@@ -56,12 +56,11 @@
     (goto-char (point-min))
     (while (< (point)(point-max))
       (decode-mime-charset-region (point)
-				  (progn
-				    (end-of-line)
-				    (point))
+				  (point-at-eol)
 				  charset)
       (end-of-line)
-      (forward-char)
+      (let ((signal-error-on-buffer-boundary nil))
+	(forward-char))
       )))
 
 

-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.

