From: Greg Stark <gsstark@mit.edu>
Cc: "(ding)" <ding@gnus.org>
Subject: Re: pop3 *very* slow?
Date: 08 Oct 1999 16:31:32 -0400 [thread overview]
Message-ID: <874sg1oaqj.fsf@HSE-Montreal-ppp19508.qc.sympatico.ca> (raw)
In-Reply-To: Stainless Steel Rat's message of "07 Oct 1999 20:14:34 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Dave Liebreich <pixiebob@bigfoot.com> on Thu, 07 Oct 1999
> | and it's *very* slow. Are the following lines in pop3.el really necessary?
>
> One, yes, those sleeps are necessary. Without them Emacs hangs on large
> messages.
Are you sure this is still true? I know emacs will accept more input during
large reads and writes now, that was done to avoid deadlocks. how is your
deadlock occurring? I'm curious because having run into this once the hard way
I would like to know what other pitfalls threaten.
--
greg
next prev parent reply other threads:[~1999-10-08 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 21:54 Dave Liebreich
1999-10-08 0:14 ` Stainless Steel Rat
1999-10-08 2:11 ` Dave Liebreich
1999-10-08 5:17 ` Dave Liebreich
1999-10-08 23:24 ` Stainless Steel Rat
1999-10-08 20:31 ` Greg Stark [this message]
1999-10-08 23:26 ` Stainless Steel Rat
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=874sg1oaqj.fsf@HSE-Montreal-ppp19508.qc.sympatico.ca \
--to=gsstark@mit.edu \
--cc=ding@gnus.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).