Gnus development mailing list
 help / color / mirror / Atom feed
From: Stefan Waldherr <swa@cs.cmu.edu>
Subject: gnus bug when editing?
Date: 21 Jul 1998 20:09:24 +0200	[thread overview]
Message-ID: <upkr9zf3wkr.fsf@amadeus.waldherr.org> (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/


             reply	other threads:[~1998-07-21 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-21 18:09 Stefan Waldherr [this message]
1998-07-22  8:46 ` XEmacs bug? [was Re: gnus bug when editing?] Jan Vroonhof

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=upkr9zf3wkr.fsf@amadeus.waldherr.org \
    --to=swa@cs.cmu.edu \
    /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).