From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: nnslashdot - quickref quide please
Date: 01 Dec 1999 16:38:11 +0100 [thread overview]
Message-ID: <m3u2m2n02k.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <764sem5agj.fsf@ppllc.com>
Jake Colman <colman@ppllc.com> writes:
> Can someone please post a quickref guide to the proper way to get up and
> running with nnslashdot? I want to play with it in the least obtrusive way
> possible so that if I don't like it I can easily remove it. Should I add the
> server through the server buffer or as a seconday-select? What is the
> easiest/best way to interact with it?
The easiest way is to put it into your secondary select methods, I think.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-12-01 15:38 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 [this message]
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
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=m3u2m2n02k.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).