Gnus development mailing list
 help / color / mirror / Atom feed
From: Alan Shutko <ats@acm.org>
Cc: ding@gnus.org
Subject: Re: mh backend
Date: 22 Sep 1998 11:18:51 -0500	[thread overview]
Message-ID: <m3emt4ruhg.fsf@hubert.wuh.wustl.edu> (raw)
In-Reply-To: Justin Sheehy's message of "22 Sep 1998 11:43:57 -400"

>>>>> "J" == Justin Sheehy <justin@linus.mitre.org> writes:

J> For some reason, a lot of people seem to think that the handy
J> little number in the *Group* buffer is a count of articles, which
J> they then conclude is incorrect.

Probably because the manual says it's the "estimated total number of
articles" rather than "a useless number dependant on other useless
numbers you don't care about".


J> Why exactly does everyone need an exact count of all of their
J> groups, anyway?  That is, how will the knowledge of exactly how
J> many messages you have change what actions you take?

If you have 50 articles in a group, and it says you have 2000, you'll
have an extra prompt on entry, which could scare you so you don't want
to waste the time and RAM that entering a 2000 msg group would give.
I also seem to remember that somewhere along the line Gnus will
consume much more memory entering a group where it thinks it has lots
of articles than where it knows it has 50.  I've had Gnus run out of
swap on my machine when our newsserver reset article numbers to some
arbitrarily high-value, even though there might have been only 50
articles... Gnus thoughtt there were a few million.

You can't make Gnus count correctly for _this_ instance, but if you
could for mail groups I'm sure things would be much happier.  Just
saying "Move all the messages back into the group" is bad advice,
because as you mentioned, you have to take special care of dormant or
ticked articles, cached articles, etc.  If it's going to mean that
much work for the user, why not fix the program?

-- 
Alan Shutko <ats@acm.org> - By consent of the corrupted
Don't read everything you believe.


  parent reply	other threads:[~1998-09-22 16:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-14 22:51 Phil Humpherys
1998-09-15  7:45 ` Kai Grossjohann
     [not found]   ` <87lnnl9msl.fsf@lemmon.iomega.com>
1998-09-16  7:31     ` Kai Grossjohann
1998-09-16  7:37       ` Phil Humpherys
     [not found] ` <x7g1dtfibe.fsf@peorth.gweep.net>
1998-09-15 18:06   ` Rajappa Iyer
1998-09-15 19:32     ` François Pinard
1998-09-15 20:34       ` Richard Coleman
1998-09-15 21:53         ` François Pinard
1998-09-15 22:43           ` Edward J. Sabol
1998-09-22 15:43           ` Justin Sheehy
1998-09-22 15:59             ` Hrvoje Niksic
1998-09-22 16:18             ` Alan Shutko [this message]
1998-09-23  8:33             ` Kai Grossjohann
1998-09-23 15:44               ` Matt Pharr
1998-09-23 16:45                 ` Kai Grossjohann
1998-09-16 15:06         ` Per Abrahamsen
1998-09-15 20:43       ` Rajappa Iyer
1998-09-15 21:47         ` Phil Humpherys
1998-09-16  8:03         ` Kai Grossjohann
1998-09-16  9:36         ` Lars Magne Ingebrigtsen
1998-09-15 21:39       ` David Hedbor
1998-09-16  8:06     ` Kai Grossjohann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3emt4ruhg.fsf@hubert.wuh.wustl.edu \
    --to=ats@acm.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).