Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!epimass!jbuck
From: jbuck@epimass.EPI.COM (Joe Buck)
Newsgroups: news.software.b
Subject: Re: Review of NN, a Usenet news reader
Keywords: rn, .newsrc, b&d
Message-ID: <3364@epimass.EPI.COM>
Date: 6 Jul 89 21:12:59 GMT
References: <1836@papaya.bbn.com> <1150@sequent.cs.qmc.ac.uk> <4827@freja.diku.dk>
Reply-To: jbuck@epimass.EPI.COM (Joe Buck)
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 28

In article <4827@freja.diku.dk> seindal@skinfaxe.diku.dk (Rene' Seindal) writes:
>Second, the discussion on the net and on the nn-info mailinglist has (in my
>eyes) revealed two major problems with nn.  The first is the `Re^n' problem,
>and I know Kim will change this if he is told often enough.  The second
>problem is the way nn marks articles as read.  The current scheme is clearly
>not sufficient, and it will have to be changed, so nn has at least facilities
>comparable to rn's.  Kim is well aware of this, and are working on it.

Great.  For me, the primary deficiency of nn is the lack of an
equivalent to rn's 'M' command -- the ability to flag certain articles
so they'll hang around and I can deal with them later -- and the ability
to stop halfway through a group, go read something else, and pick up where
I left off.  To convert the majority of rn users, nn will need to provide
this capability.  The news etiquette documents request that people
read all articles in a group before following up, to avoid duplicating
other people's words.  rn's 'M' command makes this easy.

>For those of you, that do not know, there is an nn-info mailinglist.  Send
>requests to join to nn-info-request@dkuug.dk, and submissions to
>nn-info@dkuug.dk.  As always, if you have problems or find bugs, send a
>message to nn-bugs@dkuug.dk.

If this list gets big, I suggest that a single US distribution point
be set up to save money (no, I'm not volunteering).


-- 
-- Joe Buck	jbuck@epimass.epi.com, uunet!epimass.epi.com!jbuck