Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!rpi!rpi.edu!rodney From: rodney@taac.ipl.rpi.edu (Rodney Peck II) Newsgroups: news.newusers.questions Subject: Re: Why doesn't someone create and easy to use rn? Message-ID: Date: 15 Oct 89 21:34:03 GMT References: <1085@shiva.misemi> <2831@zaphod.axion.bt.co.uk> <885@unsvax.NEVADA.EDU> <1989Oct10.235247.13717@rpi.edu> <674@wet.UUCP> Organization: Rensselaer Polytechnic Institute Image Processing Lab, Troy NY Lines: 29 In-Reply-To: epsilon@wet.UUCP's message of 15 Oct 89 01:19:37 GMT >>>>> On 15 Oct 89 01:19:37 GMT, epsilon@wet.UUCP (Eric P. Scott) said: Eric> I received mail from someone suggesting that I look at GNUS. Eric> I grabbed the sources from tut.cis.ohio-state.edu and dropped Eric> them onto a NeXT running the 1.0 release (which, interestingly Eric> enough, comes with the gnus documentation (which wasn't in 0.9), Eric> but not gnus itself). It was relatively painless to install Eric> (wow!) and worked well, if a bit slowly. I wasn't too impressed Eric> with the built-in help, but the "real" documentation is quite Eric> good. Hint: use the newsetup(1) script from rn to set up an Eric> initial .newsrc; gnus doesn't do as good a job, and takes a long Eric> time. Eric> While I personally prefer rn, there are considerable benefits to Eric> running in the GNU emacs environment, so I intend to support it. Gnus is actually much faster than rn when you use NNTP to just get headers. It really flies. What would be nicer is if it would take the time while you are reading an article to get the NEXT article. Then, response time would be seem to be practically immediate. Gnus is nice and it's extendable. -- Rodney