[1399] in SIPB bug reports
Re: GRIPE about XRN 6.13
daemon@ATHENA.MIT.EDU (dkk@ATHENA.MIT.EDU)
Wed Oct 31 05:51:48 1990
From: dkk@ATHENA.MIT.EDU
Date: Wed, 31 Oct 90 05:51:32 EST
To: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: Jonathan I. Kamens's message of Tue, 30 Oct 90 20:51:17 -0500,
> "Xrn is not rn." Rn is significantly more complicated than xrn, and
> does lots of things with environment variables that xrn doesn't do,
> so it makes sense for rn to have a -E option.
Sorry. I was under the mistaken assumption that xrn was meant to be a
more feature-ful version of rn. That said, I'll respond to a couple
of your other points anyway, just FYI.
------------
> > With "rn" I could type '=' and get a summary listing.
> I'm not sure what you're asking for here. When you go into a
> newsgroup, it automatically displays the summary listing in the top
> window, the same summary listing as the one which rn displays in
> response to '='. It has to enter the newsgroup in order to display
> the listing, so if you want '=' to display a listing, you can add
> custom key-bindings to your .Xresources to make '=' equivalent to
> ' ' (or whatever key causes it to enter the current newsgroup).
>
> Personally, I think it would be pointless to make '=' make it show a
> summary listing without entering the newsgroup. I don't feel like
Entering a newsgroup usually means marking the first message as read,
even if it was intentionally saved (marked unread last time). That
means either changing the way I read news (again) because of the
interface, or marking unread the first message of most newsgroups I go
to (each time I read news) because there's no other way to see the
headers.
But then, I'll just continue using "rn" and doing without the few
advantages of xrn, so it doesn't really matter as far as I'm
concerned.
