From: Gaute B Strokkenes <gs234@cam.ac.uk>
Subject: Re: Funny-looking code in imap.el
Date: Mon, 14 Jul 2003 09:21:57 +0100 [thread overview]
Message-ID: <87wuelsel6.fsf@cam.ac.uk> (raw)
In-Reply-To: <iluhe5py2ka.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 14 Jul 2003 09:45:09 +0200")
On 14 jul 2003, jas@extundo.com wrote:
> Gaute B Strokkenes <gs234@cam.ac.uk> writes:
>
> Is it the sit-for that delay things?
Yes, that seems to be a big part of it. Note that I haven't found a
good way to test the speed "scientifically"; this is based purely on
my eyeballing things.
> Try removing it.
That seems to work fine. Another thing that works is to hit some
harmless key, like `s', right after `g'. This works because sif-for
will not actually sit if there is pending input.
> Perhaps changing the a-p-o call to (accept-process-output process
> 0.1) would speed things up too.
Perhaps, though I doubt it. If I understand it correctly, the time
argument to a-p-o is just a timeout; it will return as soon as it gets
some output from the process or when the timeout expires, whichever
comes first. I suspect it would work just as well to use a really
big value here; the only reason to have a timeout at all seems to be
to avoid busy-looping.
--
Gaute Strokkenes http://www.srcf.ucam.org/~gs234/
I have nostalgia for the late Sixties! In 1969 I left my laundry with
a hippie!! During an unauthorized Tupperware party it was chopped &
diced!
next prev parent reply other threads:[~2003-07-14 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 2:05 Gaute B Strokkenes
2003-07-14 7:45 ` Simon Josefsson
2003-07-14 8:21 ` Gaute B Strokkenes [this message]
2003-07-14 8:34 ` Gaute B Strokkenes
2003-07-14 12:48 ` Simon Josefsson
2003-07-14 12:43 ` Kai Großjohann
2003-07-14 13:08 ` Simon Josefsson
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=87wuelsel6.fsf@cam.ac.uk \
--to=gs234@cam.ac.uk \
/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).