From: Ken McGlothlen <mcglk@artlogix.com>
Subject: Re: Wow.
Date: 01 Jun 2001 14:30:59 -0700 [thread overview]
Message-ID: <87n17r99bg.fsf@ralf.artlogix.com> (raw)
In-Reply-To: <whitih7ump.fsf@metis.no>
Steinar Bang <sb@metis.no> writes:
| >>>>> Ken McGlothlen <mcglk@artlogix.com>:
|
| > A plain ol' xemacs process takes up about 9MB, not 90MB. So is Gnus
| > really sucking up this much memory?
|
| Do you have any old nnml groups with sparse article numbers? I saw
| someone write something about the fact that expanding ranges in emacs,
| cost a lot of memory. It is very slow, at least.
Yeah, I think I do. But would old nntp groups with sparse article numbers do
the same thing? And is there a way to easily correct for that without having
to forward them though the mail system again?
prev parent reply other threads:[~2001-06-01 21:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 13:50 XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop Paul Stodghill
2001-05-21 14:09 ` Hrvoje Niksic
2001-05-21 14:37 ` Josh Huber
2001-05-21 15:05 ` Olivier Fambon
2001-05-21 15:15 ` Paul Stodghill
2001-05-21 16:07 ` Andy Piper
2001-05-21 19:13 ` Paul Stodghill
2001-05-21 19:14 ` Paul Stodghill
2001-05-28 17:45 ` fill bug still there [Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop] Paul Stodghill
2001-05-29 17:20 ` Simon Josefsson
2001-05-29 17:24 ` Paul Stodghill
2001-05-29 17:22 ` Kai Großjohann
2001-05-29 17:26 ` Paul Stodghill
2001-05-29 17:50 ` Kai Großjohann
2001-05-29 17:56 ` Paul Stodghill
2001-05-27 3:38 ` critical quit Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop Ben Wing
2001-05-28 17:44 ` Paul Stodghill
2001-05-30 1:28 ` Ben Wing
2001-05-30 7:08 ` Wow Ken McGlothlen
2001-05-30 9:26 ` Wow Kai Großjohann
2001-05-30 21:19 ` Wow Ken McGlothlen
2001-05-30 21:26 ` Wow Kai Großjohann
2001-05-31 9:10 ` Wow Steinar Bang
2001-06-01 21:30 ` Ken McGlothlen [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=87n17r99bg.fsf@ralf.artlogix.com \
--to=mcglk@artlogix.com \
/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).