From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: [PATCH] Mail fetching on memory-poor machines
Date: 15 Jul 1999 10:44:37 -0400 [thread overview]
Message-ID: <m3lncic6qy.fsf@peorth.gweep.net> (raw)
In-Reply-To: Jim Pick's message of "14 Jul 1999 20:23:36 -0700"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Jim Pick <jim@jimpick.com> on Wed, 14 Jul 1999
| I can think of several different ways of achieving a similar effect.
| For example, it might make sense for Gnus to track the size of the
| buffers currently in use, and only save the least-recently-used ones
| to disk to free up some space. That's overkill for my case though.
Perhaps... but if you were going to go this route, it might be better to be
a little more heuristic about it. That is, count how many messages are
added to each folder, and when it comes time to do some pruning, kill the
buffer with the fewest appends.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.8 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3jfPVgl+vIlSVSNkRAoRkAJ9Pt6Axw46aXWDRKJG1gd2nnlYfEQCeO3Xv
en8IF4sUdfIrL0lUHVURvGw=
=tU8D
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ When not in use, Happy Fun Ball should be
Minion of Nathan - Nathan says Hi! \ returned to its special container and
PGP Key: at a key server near you! \ kept under refrigeration.
prev parent reply other threads:[~1999-07-15 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 5:13 Jim Pick
1999-07-14 19:02 ` Stainless Steel Rat
1999-07-14 21:31 ` Jim Pick
1999-07-15 1:21 ` Stainless Steel Rat
1999-07-15 3:23 ` Jim Pick
1999-07-15 14:44 ` Stainless Steel Rat [this message]
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=m3lncic6qy.fsf@peorth.gweep.net \
--to=ratinox@peorth.gweep.net \
/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).