From: Rob Browning <rlb@cs.utexas.edu>
Subject: Tracking down a gnus-summary-move-article problem.
Date: 19 Nov 1999 02:10:00 -0600 [thread overview]
Message-ID: <87pux66gx3.fsf@raven.localnet> (raw)
I've reported this to gnus-bug, but I wanted to see if anyone else
here had see this or had suggestions for things I could try to track
this down.
I had a problem a while back with gnus-summary-move-article. It would
fail when called on an article just after a followup. After poking
around in the source, I realized it was a configuration problem on my
end (message-directory was set wrong given my other variables). I
fixed that, and then gnus-summary-move-article would get a little
further before failing in a much more serious manner.
I can't give a backtrace for the error because for some reason the
failure both doesn't give a backtrace, and disables debug-on-error,
but here's the relevant bit of the message buffer.
Opening nnml server on rlb...
Moving to nnml+rlb:gnucash: (35369)...
Loading gnus-dup...
Loading gnus-dup...done
Wrote /home/rlb/.gnus/mail/incoming/gnucash/3467
Opening nnml server on rlb+nnml+rlb:gnucash...
No such group: gnucash
nnml+rlb:gnucash error: No such group: gnucash
After this, if I quit gnus and restart, all of the nnml+rlb groups in
the group buffer will have a "*" for their message counts, and I can't
enter any of them:
Signaling: (error "Couldn't request group nnml+rlb:guile: No such group: guile")
signal(error ("Couldn't request group nnml+rlb:guile: No such group: guile"))
error("Couldn't request group %s: %s" "nnml+rlb:guile" "No such group: guile")
gnus-select-newsgroup("nnml+rlb:guile" nil nil)
gnus-summary-read-group-1("nnml+rlb:guile" nil t nil nil nil)
gnus-summary-read-group("nnml+rlb:guile" nil t nil nil nil nil)
gnus-group-read-group(nil t)
gnus-group-select-group(nil)
gnus-topic-select-group(nil)
call-interactively(gnus-topic-select-group)
The problem can be fixed by rebuilding the nov databases, but will
occur again next time I trigger the error.
Thanks
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
next reply other threads:[~1999-11-19 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-19 8:10 Rob Browning [this message]
1999-11-28 23:25 ` gnus-summary-move-article problem may be a .newsrc.eld problem Rob Browning
1999-11-29 0:17 ` Simon Josefsson
1999-11-29 4:46 ` Rob Browning
[not found] ` <81sdup$o82$1@quimby.gnus.org>
1999-12-01 18:39 ` Lars Magne Ingebrigtsen
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=87pux66gx3.fsf@raven.localnet \
--to=rlb@cs.utexas.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).