Gnus development mailing list
 help / color / mirror / Atom feed
From: Alex Schroeder <alex@gnu.org>
Subject: Re: Drafts problem
Date: 24 Feb 2001 13:31:11 +0100	[thread overview]
Message-ID: <m266i0w9dc.fsf@snail.nowhere.ch> (raw)
In-Reply-To: <2npug9hrtu.fsf@tiger.jia.vnet> (ShengHuo ZHU's message of "23 Feb 2001 19:01:33 -0500")

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> > > > Signaling: (error "Couldn't activate group nndraft:drafts: Opened server  using directory ~/News/drafts/")
> > > Have you changed the values of nnmh-* or nndir-* ?
> 
> It is a weird problem, but I don't know why.  Could you set a
> breakpoint in nnmh-request-group (it IS nnmh), then try `M-g' on
> nndraft:drafts, and tell me why it returns nil?

OK, I call debug-on-entry and enter nnmh-request-group, then I hit M-g
on the drafts group:

       *: nndraft:drafts

I get this error:

nndraft:drafts error: 

No Backtrace buffer!  nnmh-request-group is not called.



I did some feeble debugging of my own, though.  :)  Dunno wether I'm
on the correct track or not.  Here goes:  I set debug-on-error to t,
then hit M-g on the drafts group.  The error happens but no backtrace
appears.  Then I hit RET on the drafts group and I do get a
backtrace.

It happens within gnus-select-newsgroup("nndraft:drafts" nil nil)

I then try (gnus-activate-group "nndraft:drafts") and yes, it returns
nil.

Following this, I try (gnus-find-method-for-group "nndraft:drafts")
and get (nndraft "").  I proceed to check all elements in the `and'
call:

(gnus-check-server '(nndraft "")) -> t
(gnus-parse-active) -> nil

That means `active' will be nil, and therefore `gnus-activate-group'
will return nil.

(switch-to-buffer nntp-server-buffer) switches me to an empty buffer.

Maybe that is the source of the problem?

Alex.
-- 
http://www.geocities.com/kensanata/emacs.html
"Emacs 21 will be out when it comes out.  No beta available."



  reply	other threads:[~2001-02-24 12:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-23 14:22 Alex Schroeder
2001-02-23 18:22 ` Kai Großjohann
2001-02-23 21:38   ` Alex Schroeder
2001-02-23 21:45     ` ShengHuo ZHU
2001-02-23 23:41       ` Alex Schroeder
2001-02-24  0:01         ` ShengHuo ZHU
2001-02-24 12:31           ` Alex Schroeder [this message]
2001-02-25 15:17             ` ShengHuo ZHU
2001-02-25 22:53               ` Alex Schroeder
2001-02-25 23:08                 ` ShengHuo ZHU

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=m266i0w9dc.fsf@snail.nowhere.ch \
    --to=alex@gnu.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).