From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: Slowness in viewing all articles in nnfolder
Date: 01 Apr 1999 21:01:53 -0500 [thread overview]
Message-ID: <glmlngbwzji.fsf@caffeine.mitre.org> (raw)
In-Reply-To: <yj9u2uzu83y.fsf@adobe.com>
Danny Siu <dsiu@Adobe.COM> writes:
> Has anyone noticed the slowness when trying to view all articles (C-u RET RET
> in group buffer) in a nnfolder group? It took more than 5 mins for the
> summary buffer to show up! My nnfolder file (12MB!)
That is not very surprising. nnfolder is slow at generating summary
buffers, particularly on files as huge as yours.
> The reason I want to view all articles is that I like to view articles with
> ancient mark along with all unread articles. I use del-mark ("r") for
> articles I already read but want to keep around (they becomes ancient next
> time I enter the group), tick ("!") mark for articles I need to reply, and
> expirable mark ("E") for articles I want to get rid of.
It sounds to me like you haven't really adjusted to The Gnus Way of
reading your email. :-) Viewing all articles upon every group entry
isn't really the way that most Gnus users seem to read their mail.
Also, monolithic nnfolder or nnmbox groups get pretty unwieldy after a
while.
In any case, if you are really attached to that mode of operation, you
should probably switch to a backend that will be faster at doing what
you need, such as nnml.
> I don't use auto-expiry since I need to keep all ancient articles.
auto-expire does not remove ancient articles. It removes only
articles marked as 'E', and adds this mark to each article that you
read.
> Is there a way to view ONLY unread, ticked, and ancient articles?
What do you not want to see? ancient articles and read articles are
essetially the same...
--
Justin Sheehy
In a cloud bones of steel.
next prev parent reply other threads:[~1999-04-02 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-02 1:25 Danny Siu
1999-04-02 2:01 ` Justin Sheehy [this message]
1999-04-02 10:21 ` 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=glmlngbwzji.fsf@caffeine.mitre.org \
--to=justin@linus.mitre.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).