Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: nnslashdot question
Date: 06 Dec 1999 05:18:10 +0100	[thread overview]
Message-ID: <m3ln7866t9.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <761z966rhr.fsf@ppllc.com>

Jake Colman <colman@ppllc.com> writes:

> I've started using nnslashdot and it's working.  I added a
> gnus-secondary-select-method for nnslashdot and mentioned in the
> documentation.  I changed my gnus-subscribe-newsgroup-method from
> gnus-subscribe-zombies to gnus-subscribe-topics.  I created a 'slashdot'
> topic and set its parameter as described in the mail list. When I fetch
> mail/news nothing special happens unless I press "F" and then slashdot groups
> appear in the topic.
> 
> Some questions:
> 
> 1) Is what I described above the recommended way of incorporating nnslashdot?

Yes.

> 2) How do I remove slashdot groups that I am not interested in reading?  C-k?

It'll just reappear later.  Perhaps there should be a
`nnslashdot-purge-old-groups'.  Hm.  No, `G DEL' should work.  Fix in
Gnus v5.8.3.

> 3) Having changed my gnus-subscribe-newsgroup-method, how are other new
>    groups treated when they appear on my news server?  using
>    gnus-subscribe-zombies, I never did anything special to check for new
>    newsgroups. I would just periodically press A-z to check for any zombies.
>    What will be different now?

All new groups will be subscribed on level 3 in the top-level topic.
(That is, except for the groups that match some `subscription' topic
parameter.) 

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1999-12-06  4:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-02  1:50 Jake Colman
1999-12-06  4:18 ` Lars Magne Ingebrigtsen [this message]
1999-12-06 20:01   ` Jake Colman
2000-04-21 19:51     ` 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=m3ln7866t9.fsf@quimbies.gnus.org \
    --to=larsi@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).