Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Richards <cjr@netpliance.net>
Subject: Excessively Painful Forwards
Date: 16 Feb 2000 12:20:27 -0600	[thread overview]
Message-ID: <6evh3p57ro.fsf@sloth.netpliance.net> (raw)

Howdy.

S o m forwards a message.  When I tried to forward a mutli-part
message which contain a largish attachment, it took quite a well to
render the *mail* buffer.  xemacs climbed to 97% of the CPU and 49% of
available memory.

When it finished churning, I realized why... the entire attachment was
shown encoded in the buffer.

Is there away to _hide_ such attachments?  Knowing they are there in
buttonized form would be nice--anything to speed up the access.

On a related note, gnus hangs my xemacs session when it
checks/parses/splits news and mail.  Is this a limitation of the
architecture or this there a way to background these tasks?

Cheers,
cjr



             reply	other threads:[~2000-02-16 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-16 18:20 Chris Richards [this message]
2000-02-16 22:13 ` Kai Großjohann
2000-04-10  3:08   ` Greg Stark
2000-04-10  7:52     ` Kai Großjohann

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=6evh3p57ro.fsf@sloth.netpliance.net \
    --to=cjr@netpliance.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).