Gnus development mailing list
 help / color / mirror / Atom feed
* gnus bug when editing?
@ 1998-07-21 18:09 Stefan Waldherr
  1998-07-22  8:46 ` XEmacs bug? [was Re: gnus bug when editing?] Jan Vroonhof
  0 siblings, 1 reply; 2+ messages in thread
From: Stefan Waldherr @ 1998-07-21 18:09 UTC (permalink / raw)


Hi,

I recently observed the following bug: select an article, hit `e' to edit,
edit something, then `C c' to finish. Selecting another article yields

(85) (warning/warning) Error caught in `font-lock-pre-idle-hook'

in the message line. Debug output is 

Signaling: (wrong-type-argument extent-live-p #<destroyed extent>)
  extent-start-position(#<destroyed extent>)
  font-lock-after-change-function(1 1 2111)
  erase-buffer()
  gnus-request-article-this-buffer(91 "nnml:timm")
  gnus-article-prepare(91 nil)
  gnus-summary-display-article(91 nil)
  gnus-summary-select-article(nil nil pseudo)
  gnus-summary-scroll-up(1)
  call-interactively(gnus-summary-scroll-up)

Anyone?

Thanks,
Stefan.
-- 
Stefan Waldherr                   fax +49 431 8058 136
                               e-Mail swa@cs.cmu.edu
                                  www http://www.waldherr.org/


^ permalink raw reply	[flat|nested] 2+ messages in thread

* XEmacs bug? [was Re: gnus bug when editing?]
  1998-07-21 18:09 gnus bug when editing? Stefan Waldherr
@ 1998-07-22  8:46 ` Jan Vroonhof
  0 siblings, 0 replies; 2+ messages in thread
From: Jan Vroonhof @ 1998-07-22  8:46 UTC (permalink / raw)
  Cc: xemacs-patches

Stefan Waldherr <swa@cs.cmu.edu> writes:

> I recently observed the following bug: select an article, hit `e' to edit,
> edit something, then `C c' to finish. Selecting another article yields
> 
> (85) (warning/warning) Error caught in `font-lock-pre-idle-hook'

I cannot reproduce this with 21.x, but I think I can see what the problem is.

> Signaling: (wrong-type-argument extent-live-p #<destroyed extent>)
>   extent-start-position(#<destroyed extent>)
>   font-lock-after-change-function(1 1 2111)

It is a bug in the XEmacs font-lock-pre-idle-hook, does this "obviously
correct"  patch help:

1998-07-22  Jan Vroonhof  <vroonhof@math.ethz.ch>

	* font-lock.el (font-lock-fontify-glumped-region): Add guard
	aginst destroyed extents


Index: font-lock.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs-20/lisp/font-lock.el,v
retrieving revision 1.7
diff -u -u -r1.7 font-lock.el
--- font-lock.el	1998/06/20 00:58:20	1.7
+++ font-lock.el	1998/07/22 16:29:22
@@ -1073,8 +1073,9 @@
   ;; region as fontified; otherwise, the same error might get signaled
   ;; after every command.
   (unwind-protect
-      ;; buffer may be deleted.
-      (if (buffer-live-p (extent-object font-lock-old-extent))
+      ;; buffer/extent may be deleted.
+      (if (and (extent-live-p font-lock-old-extent)
+	       (buffer-live-p (extent-object font-lock-old-extent)))
 	  (save-excursion
 	    (set-buffer (extent-object font-lock-old-extent))
 	    (font-lock-after-change-function-1





^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~1998-07-22  8:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-07-21 18:09 gnus bug when editing? Stefan Waldherr
1998-07-22  8:46 ` XEmacs bug? [was Re: gnus bug when editing?] Jan Vroonhof

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).