From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Drafts problem
Date: 25 Feb 2001 18:08:29 -0500 [thread overview]
Message-ID: <5br90mqs2a.fsf@curlew.cs.rochester.edu> (raw)
In-Reply-To: <m2y9uuxtlj.fsf@snail.nowhere.ch> (Alex Schroeder's message of "25 Feb 2001 23:53:28 +0100")
Alex Schroeder <alex@gnu.org> writes:
> > Alex Schroeder <alex@gnu.org> writes:
> >
> > > 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.
>
> OK, what I did now is the following: I read some news, read some
> mail, then I hit RET on the group
> *: nndraft:drafts
> and get the error "Couldn't activate group nndraft:drafts: ". I then
> evaluate (switch-to-buffer nntp-server-buffer) and this is the buffer
> contents:
>
> icann.members.announce 11 1 y
[...]
>
> Does that help at all?
It seems that they are from another server. What is that? Can you
post the group info of nndraft:drafts (hit `G E' on the group) and the
value of nnoo-state-alist after hitting RET on the group? (If the
size of the value is large, send it to me.)
ShengHuo
prev parent reply other threads:[~2001-02-25 23:08 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
2001-02-25 15:17 ` ShengHuo ZHU
2001-02-25 22:53 ` Alex Schroeder
2001-02-25 23:08 ` ShengHuo ZHU [this message]
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=5br90mqs2a.fsf@curlew.cs.rochester.edu \
--to=zsh@cs.rochester.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).