From: Jake Colman <colman@ppllc.com>
Cc: ding@gnus.org
Subject: Re: nnslashdot - quickref quide please
Date: 07 Dec 1999 23:25:00 -0500 [thread overview]
Message-ID: <76u2luxdnn.fsf@ppllc.com> (raw)
In-Reply-To: Jack Vinson's message of "06 Dec 1999 21:53:16 -0600"
>>>>> "JV" == Jack Vinson <vinson@unagi.cis.upenn.edu> writes:
>>>>> "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
KG> that they will be subscribed under the top-level topic at the default
KG> subscription level.
JV> According to the info page '(gnus)Subscription Methods',
JV> gnus-subscribe-topics will do exactly the same as
JV> gnus-subscribe-randomly EXCEPT for new groups which match the
JV> 'subscribe' Topic parameter.
So what's the bottom line then? Where did they end up? I see from my
message log that 31 new groups arrived yesterday and 500+ new groups (!)
arrived today. I _know_ that they are not all slashdot! So how can I find
them? And how do I make sure they don't disappear next time?
JV> My slashdot Topic parameter looks like this: ((score-file
JV> . "nnslashdot.all.SCORE")
JV> (subscribe . "nnslashdot"))
JV> The slashdot.all.SCORE has fun things like increasing score for
JV> Interersting, Funny, Insightful, Informative. And decrease score on
JV> Redundant, Flamebait and Offtopic.
I'd love to see how you are using SCORE files. I think this is something
I'd love to start to use but am not certain how/where to begin.
--
Jake Colman
Principia Partners LLC Phone: (201) 946-0300
Harborside Financial Center Fax: (201) 946-0320
902 Plaza II Beeper: (800) 505-2795
Jersey City, NJ 07311 E-mail: colman@ppllc.com
E-mail: jcolman@jnc.com
web: http://www.ppllc.com
"Every time I think I've idiot-proofed something someone comes up with a
better idiot"
next prev parent reply other threads:[~1999-12-08 4:25 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
1999-12-07 18:39 ` dave-mlist
1999-12-08 4:25 ` Jake Colman [this message]
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=76u2luxdnn.fsf@ppllc.com \
--to=colman@ppllc.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).