From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: nnslashdot
Date: 09 Nov 1999 01:19:08 -0500 [thread overview]
Message-ID: <2nn1sow5k3.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Matt Pharr's message of "08 Nov 1999 22:32:50 -0800"
>>>>> "Matt" == Matt Pharr <mmp@graphics.stanford.edu> writes:
Matt> Some more information. It turns out that all of the slashdot
Matt> articles were zombified. Preivously I had
Matt> gnus-subscribe-newsgroup-method as the default
Matt> gnus-subscribe-zombies; the only other subscribing variable I
Matt> had set was
Matt> (setq gnus-subscribe-hierararchical-interactive t)
Matt> I was able to do A z in the group buffer and subscribe to those
Matt> guys and successfully read slashdot stuff--wheee!
Matt> I've now changed gnus-subscribe-newsgroup-method to
Matt> gnus-subscribe-randomly; I suspect that that will fix things and
Matt> will report back once slashdot has posted something new and I
Matt> see if that's the case.
Lars did a trick `gnus-subscribe-topics' here.
I use it as following,
1. (setq gnus-subscribe-newsgroup-method 'gnus-subscribe-topics)
2. (add-hook 'gnus-group-mode-hook 'gnus-topic-mode) ;; be sure using topics
3. `T n' to create a topic named "slashdot"
4. `G p' on the topic
5. Put ((subscribe . "nnslashdot")) as topic parameters
For details, check the info node.
Matt> Now my next question: how to reliably make the original slashdot
Matt> article be the first thing in the summary buffer?
The original article should be article number 1 in the group. If
you've read the article, it may not be the first one in the summary
buffer.
--
Shenghuo
next prev parent reply other threads:[~1999-11-09 6:19 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-07 6:32 nnslashdot Lars Magne Ingebrigtsen
1999-11-07 6:42 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-08 22:51 ` nnslashdot Dan Christensen
1999-11-08 22:59 ` nnslashdot Shenghuo ZHU
1999-11-08 23:23 ` nnslashdot Dan Christensen
1999-11-08 23:57 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 0:35 ` nnslashdot Matt Pharr
1999-11-08 23:53 ` nnslashdot Dan Christensen
1999-11-09 0:09 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 1:15 ` nnslashdot Matt Pharr
1999-11-09 0:37 ` nnslashdot Matt Pharr
1999-11-09 0:17 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 1:17 ` nnslashdot Matt Pharr
1999-11-09 0:23 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 6:32 ` nnslashdot Matt Pharr
1999-11-09 6:19 ` Shenghuo ZHU [this message]
1999-11-10 20:55 ` nnslashdot Matt Pharr
1999-11-10 21:56 ` nnslashdot Kai Großjohann
1999-11-11 1:39 ` nnslashdot is great, shame about the content David Maslen
1999-11-11 15:22 ` Laura Conrad
1999-11-11 17:12 ` Raja R Harinath
1999-11-12 7:11 ` Lars Magne Ingebrigtsen
1999-11-11 16:35 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-11 23:08 ` nnslashdot Matt Pharr
1999-11-12 4:30 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-12 6:16 ` nnslashdot Norbert Koch
1999-11-12 8:03 ` nnslashdot Hrvoje Niksic
1999-11-12 8:26 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-12 10:16 ` nnslashdot Steinar Bang
1999-11-12 11:01 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-14 15:42 ` nnslashdot Jack Twilley
1999-11-15 19:51 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-16 19:25 ` nnslashdot Jack Twilley
1999-12-01 15:20 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 21:03 ` nnslashdot Kevin Ryde
1999-11-08 23:51 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 0:58 ` nnslashdot Matt Pharr
1999-11-09 0:07 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-09 1:09 ` nnslashdot Matt Pharr
1999-11-09 4:29 ` nnslashdot Dan Christensen
1999-11-09 14:23 ` nnslashdot Lars Magne Ingebrigtsen
1999-11-10 4:54 ` nnslashdot Dan Christensen
-- strict thread matches above, loose matches on Subject: below --
2000-05-11 11:08 nnslashdot Lars Magne Ingebrigtsen
2000-05-11 15:05 ` nnslashdot BrYan P. Johnson
2000-05-11 15:13 ` nnslashdot BrYan P. Johnson
2000-05-11 15:19 ` nnslashdot dme
2000-05-12 15:49 ` nnslashdot Kai Großjohann
2000-05-12 16:27 ` nnslashdot Alan Shutko
2000-05-12 17:28 ` nnslashdot Kai Großjohann
1999-11-07 19:35 nnslashdot Lars Magne Ingebrigtsen
1999-11-08 4:19 ` nnslashdot Shenghuo ZHU
1999-07-07 7:16 nnslashdot Lars Magne Ingebrigtsen
1999-07-07 7:16 ` nnslashdot David Hedbor
1999-07-07 7:42 ` nnslashdot Lars Magne Ingebrigtsen
1999-07-07 12:08 ` nnslashdot Chris Halverson
1999-07-07 18:30 ` nnslashdot David Hedbor
1999-07-07 10:47 ` nnslashdot Jon K Hellan
1999-07-09 17:17 ` nnslashdot Lars Magne Ingebrigtsen
1999-07-07 20:56 ` nnslashdot Wes Hardaker
1999-07-07 22:55 ` nnslashdot David Hedbor
1999-07-08 11:31 ` nnslashdot Kai.Grossjohann
1999-07-08 22:16 ` nnslashdot David Hedbor
1999-07-09 17:23 ` nnslashdot Lars Magne Ingebrigtsen
1999-07-09 17:24 ` nnslashdot Ted Rathkopf
1999-07-12 13:01 ` nnslashdot Jan Vroonhof
1999-08-27 17:36 ` nnslashdot Lars Magne Ingebrigtsen
1999-07-12 15:44 ` nnslashdot Wes Hardaker
1999-07-12 20:13 ` nnslashdot Simon Josefsson
1999-07-12 21:09 ` nnslashdot Wes Hardaker
1999-07-13 0:48 ` nnslashdot Rob Browning
1999-07-13 11:20 ` nnslashdot Kim-Minh Kaplan
1999-07-13 12:45 ` nnslashdot Simon Josefsson
1999-07-21 22:29 ` nnslashdot Carl R. Witty
1999-07-26 11:59 ` nnslashdot Kim-Minh Kaplan
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=2nn1sow5k3.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.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).