From: Michael Shields <shields@msrl.com>
Cc: ding@gnus.org
Subject: Re: Making all nnml groups visible
Date: 09 Jan 2001 22:19:56 +0000 [thread overview]
Message-ID: <87bstg9xmb.fsf@challah.msrl.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "05 Jan 2001 15:37:03 +0100"
> On 04 Jan 2001, Michael Shields wrote:
>
> > However, new nnml groups -- i.e., by creating a file in
> > ~/Gnuspool/.incoming -- don't seem to appear in the group buffer.
> > If I add them with `j', they appear as killed. I'd like them to be
> > subscribed. How can I do this?
>
> What happens when you do `F'?
It reads the active file from nntp, then says "8406 new groups have
arrived". Otherwise nothing changes.
> Also see
> gnus-subscribe-newsgroup-method, that tells Gnus what to do with new
> groups. Maybe you have to hit `A z' for those?
I have:
(setq gnus-subscribe-newsgroup-method 'gnus-subscribe-topics)
`A z' says "No zombie groups".
--
Shields.
next prev parent reply other threads:[~2001-01-09 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 23:44 Michael Shields
2001-01-05 14:37 ` Kai Großjohann
2001-01-09 22:19 ` Michael Shields [this message]
2001-01-09 23:20 ` Kai Großjohann
2001-01-06 15:35 ` NAGY Andras
2001-01-09 22:37 ` Alan Shutko
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=87bstg9xmb.fsf@challah.msrl.com \
--to=shields@msrl.com \
--cc=ding@gnus.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).