From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: [ShengHuo ZHU <zsh@cs.rochester.edu>] Re: (void-function overlay-lists)
Date: 06 Oct 2000 15:55:35 +0200 [thread overview]
Message-ID: <vafbswy5b1k.fsf@lucy.cs.uni-dortmund.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
The following message contains two `Rene ... writes:' lines. The
first one is blue, the second one is black. Do you also see that?
Why does it happen?
(Also, the first `writes:' is a button, the second isn't.)
kai
--
I like BOTH kinds of music.
[-- Attachment #2: Type: message/rfc822, Size: 3222 bytes --]
From: ShengHuo ZHU <zsh@cs.rochester.edu>
To: ding@gnus.org
Subject: Re: (void-function overlay-lists)
Date: Fri, 6 Oct 2000 08:36:31 -0400
Message-ID: <200010061236.e96CaV515217@zsh.2y.net>
"Rene H. Larsen" <rhl@traceroute.dk> writes:
> With current CVS gnus I get this backtrace when trying to access any
> article:
>
> Signaling: (void-function overlay-lists)
> overlay-lists()
> gnus-kill-all-overlays()
> gnus-request-article-this-buffer(3977 "nnimap+mail:lists.gnus.ding")
> gnus-article-prepare(3977 nil)
> gnus-summary-display-article(3977 nil)
> gnus-summary-select-article(nil nil pseudo)
> gnus-summary-scroll-up(1)
> call-interactively(gnus-summary-scroll-up)
>
> This is on XEmacs 21.1.12.
"Rene H. Larsen" <rhl@traceroute.dk> writes:
> After having sent this bug report it "magically" worked until I
> restarted XEmacs, and then it complained again. I suppose someone
> forgot a (require 'overlay) somewhere.
gnus-kill-all-overlays should be an alias of
gnus-xmas-kill-all-overlays (in gnus-xmas.el) when Gnus runs in
XEmacs, so XEmacs' FSF compatible overaly package is not required.
But it possibly is a problem of loading order. Could you check why
gnus-util.el is loaded after gnus-xmas.el?
ShengHuo
next reply other threads:[~2000-10-06 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-06 13:55 Kai Großjohann [this message]
2000-10-06 16:20 ` ShengHuo ZHU
2000-10-06 16:46 ` Kai Großjohann
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=vafbswy5b1k.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).