From: SL Baur <steve@xemacs.org>
Subject: Re: Problem with Groups of the same name under different backends
Date: 24 Aug 1998 16:57:42 -0700 [thread overview]
Message-ID: <m2d89que4p.fsf@altair.xemacs.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "23 Aug 1998 14:26:49 +0200"
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
Lars Magne Ingebrigtsen <larsi@gnus.org> writes in ding@gnus.org:
> SL Baur <steve@xemacs.org> writes:
>> And, of course, XEmacs 19.16 failed the same way XEmacs 21.0 and Emacs
>> 20.2 do.
>>
>> (gnus-group-set-info '("gnu.misc.discuss" 3 ((1 . 2872) (2874 . 2885))))
>> (gnus-group-set-info '("gnu.misc.discuss" 3 ((1 . 2872) (2874 . 2885))))
>> (gnus-group-set-info '("gnu.misc.discuss" 3 ((1 . 2474))))
> Hm... Does this group have a cache, by any chance?
No. I will never use caches again after the server renumbering fiasco.
> Anyway, could you debug-on-entry `gnus-dribble-enter' and send me the
> three backtraces produced?
I'm going to try an unbytecompiled version next and email it to you
off-list.
[-- Attachment #2: 3dumps.txt --]
[-- Type: text/plain, Size: 1797 bytes --]
Entering:
* gnus-dribble-enter("(gnus-group-set-info '(\"gnu.misc.discuss\" 3 ((1 . 2894))))")
gnus-summary-move-article(nil nil nil copy)
gnus-summary-copy-article(nil)
call-interactively(gnus-summary-copy-article)
Entering:
* gnus-dribble-enter("(gnus-group-set-info '(\"gnu.misc.discuss\" 3 ((1 . 2894))))")
gnus-group-update-group("gnu.misc.discuss")
gnus-group-get-new-news-this-group(1 t)
gnus-summary-move-article(nil nil nil copy)
gnus-summary-copy-article(nil)
call-interactively(gnus-summary-copy-article)
Entering:
* gnus-dribble-enter("(gnus-group-set-info '(\"gnu.misc.discuss\" 3 ((1 . 2518))))")
gnus-group-update-group("gnu.misc.discuss")
gnus-summary-update-info()
#<compiled-function (&optional temporary) "...(541)" [gnus-set-global-variables gnus-kill-save-kill-buffer gnus-async-halt-prefetch gnus-newsgroup-name group gnus-group-quit-config quit-config major-mode mode nil group-point buf gnus-run-hooks gnus-summary-prepare-exit-hook gnus-single-article-buffer gnus-original-article-buffer buffer get-buffer buffer-name kill-buffer gnus-article-current gnus-use-cache gnus-cache-possibly-remove-articles gnus-cache-save-buffers gnus-async-prefetch-remove-group gnus-suppress-duplicates gnus-dup-enter-articles gnus-use-trees gnus-tree-close nnmail-purge-split-history gname string-match "^[^:]+:" 0 gnus-exit-group-hook gnus-summary-update-info gnus-newsgroup-adaptive gnus-score-adaptive gnus-use-scoring gnus-score-save gnus-close-group gnus-group-buffer gnus-group-jump-to-group gnus-summary-exit-hook gnus-group-group-name gnus-group-next-unread-group 1 temporary gnus-article-buffer gnus-kill-summary-on-exit ...] 5 ("/usr/local/lib/xemacs/xe
m!
!
!
!
acs-packages/lisp/gnus/gnus-sum.elc" . 135299) nil>()
call-interactively(gnus-summary-exit)
next prev parent reply other threads:[~1998-08-24 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-22 22:03 SL Baur
1998-08-23 0:59 ` Lars Magne Ingebrigtsen
1998-08-23 1:38 ` SL Baur
1998-08-23 2:04 ` Lars Magne Ingebrigtsen
1998-08-23 3:38 ` SL Baur
1998-08-23 3:49 ` SL Baur
1998-08-23 12:26 ` Lars Magne Ingebrigtsen
1998-08-24 23:57 ` SL Baur [this message]
1998-08-23 3:35 ` SL Baur
1998-08-23 10:54 ` Hrvoje Niksic
1998-08-23 12:04 ` Lars Magne Ingebrigtsen
1998-08-24 9:21 ` Kai Grossjohann
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=m2d89que4p.fsf@altair.xemacs.org \
--to=steve@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).