karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) (11/16/88)
Using spool configuration, with an NNTP inews for posting; 18.52 on a
Sun3/50.
I had just finished reading my news, so I had used `q' to leave the
last article of the last group (in gnu.emacs.gnus, as it happened),
putting me back in my *Newsgroups* buffer, now showing, e.g.:
0: misc.jobs.misc
0: news.groups
0: news.sysadmin
0: gnu.emacs
0: gnu.emacs.gnus
I inadvertently typed `=', which caused GNUS to go off and collect
headers again for a *Subject* buffer. Now, since I had finished
reading all articles in gnu.emacs.gnus, I would have presumed that it
would have come up with an empty *Subject* buffer, but instead I got
*all* articles currently in-spool, with them all marked D.
Is this what was intended in such a circumstance, or have I found a
bug?
-=-
"He even writes obnoxious LISP CODE!"
-- A local Lisp hacker and AI expert, having tried
(thus far unsuccessfully) to bring up Gnews 2.0.umerin@UUNET.UU.NET (Masanobu UMEDA) (11/17/88)
Date: 16 Nov 88 15:07:29 GMT From: flab!fgw!uunet!triceratops.cis.ohio-state.edu!karl (Karl Kleinpaste) Organization: OSU I inadvertently typed `=', which caused GNUS to go off and collect headers again for a *Subject* buffer. Now, since I had finished reading all articles in gnu.emacs.gnus, I would have presumed that it would have come up with an empty *Subject* buffer, but instead I got *all* articles currently in-spool, with them all marked D. Is this what was intended in such a circumstance, or have I found a bug? It is a feature, not a bug. Masanobu UMEDA umerin@flab.flab.Fujitsu.JUNET umerin%flab.flab.Fujitsu.JUNET@uunet.uu.NET
karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) (11/18/88)
kddlab!photon.stars.flab.fujitsu.junet!umerin@UUNET.UU.NET (Masanobu UMEDA) writes:
[I described a problem where `=' on a newsgroup with 0 articles
caused GNUS to go collect all the newsgroup's headers.]
It is a feature, not a bug.
I understand the rationale behind doing such a thing, but I must say
that it is bound to cause problems sometimes, in heavy-traffic
newsgroups that are expired seldom. As a case in point, we expire on
a six-week basis - an entire Eagle's worth of news, maintained at
about 75-80% full. My news host currently has 1200 articles in-spool
for comp.unix.wizards, 2500 for talk.bizarre, and some 4400 in
talk.politics.misc. The feature is good, but perhaps it needs a
size-limiting variable.
--Karl
-=-
"He even writes obnoxious LISP CODE!"
-- A local Lisp hacker and AI expert, having tried
(thus far unsuccessfully) to bring up Gnews 2.0.umerin@UUNET.UU.NET (Masanobu UMEDA) (11/29/88)
Date: 17 Nov 88 17:25:52 GMT
From: flab!fgw!uunet!triceratops.cis.ohio-state.edu!karl (Karl Kleinpaste)
Organization: OSU
References: <KARL.88Nov16100729@triceratops.cis.ohio-state.edu>, <8811170758.AA01163@photon.stars.flab.fujitsu.junet>
kddlab!photon.stars.flab.fujitsu.junet!umerin@UUNET.UU.NET (Masanobu UMEDA) writes:
[I described a problem where `=' on a newsgroup with 0
articles caused GNUS to go collect all the newsgroup's
headers.]
It is a feature, not a bug.
My news host currently has 1200 articles in-spool
for comp.unix.wizards, 2500 for talk.bizarre, and some 4400 in
talk.politics.misc. The feature is good, but perhaps it needs a
size-limiting variable.
Next version of GNUS (probably 3.11) will ask the number of articles
to be selected in such large newsgroups.
Masanobu UMEDA
umerin@flab.Fujitsu.JUNET
umerin%flab.Fujitsu.JUNET@uunet.uu.NET