Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!bionet!agate!pasteur!ames!vsi1!daver!mfgfoc!exodus
From: exodus@mfgfoc.uucp (Greg Onufer)
Newsgroups: comp.sources.d
Subject: Re: vn verses vnews
Message-ID: <442@mfgfoc.uucp>
Date: 14 Oct 88 03:45:10 GMT
References: <539@comdesign.CDI.COM>
Organization: Focus Semiconductor Sys, Sunnyvale
Lines: 21

From article <539@comdesign.CDI.COM>, by pst@comdesign.CDI.COM (Paul Traina):
> the reading of groups one at a time (a *big* loss of vn is that it scans
> and reads every message header in every group at once.  This is bogus
> behavior)).

Depends on the operating system you are running, actually (it always
comes down to that, doesn't it? :-)  If you have job control, vn's
mis-feature becomes a win... it is intelligent enough not to do
stupid things in the background during its news gathering phase, like try
to output to the terminal!  Thus, one merely starts it up, suspends it,
then places it in the background while one reads his/her mail.  It
will eventually attempt I/O when it is finished and you get a little
blurb from your shell ([1] Stopped Output   vn  -- or whatever) and
you then place the job in the foreground.  But that's only on my home
machine, here at work with Sys V, I just have to wait and wait and wait!

Now if someone would get vn to behave like vnews with cross-postings,
behave like rn with kill-files, and sort the headers, life would be 
wonderful.  Anyone up to it?

-Greg