Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Vinson <vinson@unagi.cis.upenn.edu>
Subject: Re: nnslashdot - quickref quide please
Date: 06 Dec 1999 21:53:16 -0600	[thread overview]
Message-ID: <wkzovn4dar.fsf@unagi.cis.upenn.edu> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "06 Dec 1999 23:39:56 +0100"

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

KG> Jake Colman <colman@ppllc.com> writes:
>> [...] The question I have now is what happens to my new
>> non-nnslashdot groups? [...]

KG> I had been thinking about that one, too.  I recall that Lars said that
KG> they will be subscribed under the top-level topic at the default
KG> subscription level. 

According to the info page '(gnus)Subscription Methods',
gnus-subscribe-topics will do exactly the same as gnus-subscribe-randomly
EXCEPT for new groups which match the 'subscribe' Topic parameter.

My slashdot Topic parameter looks like this:
((score-file . "nnslashdot.all.SCORE")
 (subscribe . "nnslashdot"))

The slashdot.all.SCORE has fun things like increasing score for
Interersting, Funny, Insightful, Informative.  And decrease score on
Redundant, Flamebait and Offtopic.  

-- 
Jack Vinson <jvinson@chevax.ecs.umass.edu>    http://www.cis.upenn.edu/~vinson/
Zippy: I guess we can live on his POT FARM in HADES!!



  reply	other threads:[~1999-12-07  3:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-16 22:38 Jake Colman
1999-11-16 22:44 ` Kai Großjohann
1999-12-01 15:38 ` Lars Magne Ingebrigtsen
1999-12-01 23:42   ` Jake Colman
1999-12-05 22:13     ` Kai Großjohann
1999-12-06 19:54       ` Jake Colman
1999-12-06 22:39         ` Kai Großjohann
1999-12-07  3:53           ` Jack Vinson [this message]
1999-12-07 18:39             ` dave-mlist
1999-12-08  4:25             ` Jake Colman
1999-12-08  5:29               ` Jack Vinson
1999-12-10 11:27             ` Peter Makholm

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=wkzovn4dar.fsf@unagi.cis.upenn.edu \
    --to=vinson@unagi.cis.upenn.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).