From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] an enormously long time to save a message
Date: Tue, 11 Sep 2007 12:34:05 -0700 [thread overview]
Message-ID: <1189539108-sup-741@south> (raw)
In-Reply-To: <1189190953-sup-2994@mona>
Excerpts from jeff.covey's message of Fri Sep 07 11:52:22 -0700 2007:
> i received a message with 8mb of text. i tried to save it to a file,
> and sup took the load on my computer past 10. i gave it five minutes
> of grinding my hard drive, then killed it. i opened the source in
> mutt, and it saved it in about half a second.
I think I've sped this up. Untested, of course. And note that Sup will
never be anywhere as fast as Mutt, at least until I start using
RubyInline to drop in some C code. :)
In particular saving large attachments worries me, because who knows
what RubyMail is doing...
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-09-11 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 18:52 jeff covey
2007-09-11 19:34 ` William Morgan [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=1189539108-sup-741@south \
--to=wmorgan-sup@masanjin.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