From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: new groups are split, but not displayed automatically
Date: 02 Dec 1999 14:04:50 +1100 [thread overview]
Message-ID: <t4iiu2ivy99.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: dave-mlist@bfnet.com's message of "Wed, 01 Dec 1999 20:22:18 -0500"
>>>>> "dave-mlist" == dave-mlist <dave-mlist@bfnet.com> writes:
>> > But when I'm looking at my *Group* buffer, the newly created
>> group is > not listed.
>>
>> The `F' command will query backends for new groups and
>> subscribe them.
dave-mlist> No, actually it doesn't. I just tried it. I had a
dave-mlist> new nnml group called "linux-kernel" which I was not
dave-mlist> subscribed to. I pressed "F" and it said something
The F command always has worked for me (PGnus 0.98). Perhaps
something broke in 0.99?
Otherwise, does restarting PGnus (with R) or exiting and
restarting show the group?
dave-mlist> like "No new newsgroups." Then I pressed "j <space>"
dave-mlist> and saw linux-kernel in the list. I typed
dave-mlist> "linux-kernel" and hit return. The linux-kernel group
dave-mlist> popped up with many unread messages, and was marked
dave-mlist> with a "Z" in the *Groups* buffer. I typed a "U" to
dave-mlist> subscribe the group (ironic), and was finally able to
dave-mlist> read it. There has to be an easier way!
I have observed that behavour in 0.98, too. A bit strange that
the group is marked as a zombie, when it should be subscribed
automatically, but I can live with that.
--
Brian May <bmay@csse.monash.edu.au>
next prev parent reply other threads:[~1999-12-02 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 1:11 dave-mlist
1999-12-02 1:23 ` Lars Magne Ingebrigtsen
1999-12-02 1:22 ` dave-mlist
1999-12-02 3:04 ` Brian May [this message]
1999-12-06 4:06 ` Lars Magne Ingebrigtsen
1999-12-02 19:53 ` dave-mlist
1999-12-02 22:43 ` Gerd Boerrigter
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=t4iiu2ivy99.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).