From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: nnslashdot usage
Date: 11 Nov 1999 16:47:49 -0500 [thread overview]
Message-ID: <5bn1skya2i.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: <m37ljoomfw.fsf@quicksilver.bzl.bzl>
>>>>> "BZL" == Bruce Z Lysik <eldrik@logrus.com> writes:
BZL> Hi guys,
BZL> So I've made the jump to the CVS version of pgnus, and I've a question
BZL> regarding nnslashdot.
BZL> The info file recommends:
BZL> (setq gnus-secondary-select-methods
BZL> '((nnslashdot "")))
BZL> and then using 'F' to subscribe to the subsequent groups.
BZL> Currently I have have an nnml secondary select method. Thinking I
BZL> could just have multiple methods, I tried:
BZL> (setq gnus-secondary-select-methods
BZL> '((nnml "private")
BZL> (nnslashdot "")))
BZL> Unfortunately this didn't seem to do anything, as hitting 'F' resulted
BZL> in no new groups appearing.
BZL> Am I going about this the wrong way?
It seems correct. Are you sure you've updated to the latest CVS, since
nnslashdot.el is fixed so frequently? In case `F' doesn't work, try
to browse the newsgroups in the Server buffer (type `^' in Group
buffer).
>>>>> "BZL" == Bruce Z Lysik <eldrik@logrus.com> writes:
BZL> Hi there!
BZL> I remembering reading on ding sometime ago you mentioning a trick
BZL> to manage nnslashdot via a topic.
BZL> Do you remember what I'm talking about? I've been playing with
BZL> nnslashdot, and it seems very unwieldy as is.
[...]
I just said how to put the new slashdot groups into a topic.
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-11-11 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-11 19:30 Bruce Z. Lysik
1999-11-11 21:47 ` Shenghuo ZHU [this message]
1999-11-11 22:00 ` Laura Conrad
1999-11-11 22:06 ` Bruce Z. Lysik
2001-12-09 22:15 Ami Fischman
2001-12-10 17:36 ` ShengHuo ZHU
2001-12-10 19:07 ` Ami Fischman
2001-12-10 19:41 ` ShengHuo ZHU
2001-12-11 20:43 ` Ami Fischman
2001-12-11 9:39 ` Kai Großjohann
2001-12-11 17:34 ` Ami Fischman
2001-12-29 0:55 ` Lars Magne Ingebrigtsen
2001-12-29 2:21 ` ShengHuo ZHU
2001-12-29 2:34 ` 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=5bn1skya2i.fsf@giga.cs.rochester.edu \
--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).