From: Jan Vroonhof <vroonhof@math.ethz.ch>
Cc: xemacs-patches@xemacs.org
Subject: XEmacs bug? [was Re: gnus bug when editing?]
Date: 22 Jul 1998 10:46:13 +0200 [thread overview]
Message-ID: <byaf62l1d6.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Stefan Waldherr's message of "Tue, 21 Jul 1998 18:30:55 GMT"
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
prev parent reply other threads:[~1998-07-22 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-21 18:09 gnus bug when editing? Stefan Waldherr
1998-07-22 8:46 ` Jan Vroonhof [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=byaf62l1d6.fsf@bolzano.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
--cc=xemacs-patches@xemacs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).