Gnus development mailing list
 help / color / mirror / Atom feed
From: Gaute B Strokkenes <gs234@cam.ac.uk>
Subject: Funny-looking code in imap.el
Date: Mon, 14 Jul 2003 03:05:38 +0100	[thread overview]
Message-ID: <87znjhsw0d.fsf@cam.ac.uk> (raw)

Having recently switched to using imap over ssl as a mail-source (as
opposed to fetchmail), I have been a bit annoyed at the amount of time
it can take to say `g' now that I have two extra imap-over-ssl
mail-sources.

Looking at imap-ssl-open in imap.el:

	    (while (and (memq (process-status process) '(open run))
			(set-buffer buffer) ;; XXX "blue moon" nntp.el bug
			(goto-char (point-max))
			(forward-line -1)
			(not (imap-parse-greeting)))
	      (accept-process-output process 1)
	      (sit-for 1))

I find the sit-for here rather surprising, though this bit of the
logic is duplicated in the other imap-foo-open functions, so it's
clearly not by mistake.  The elisp manual states that the typical use
of sit-for is to give the user time to read a message; that doesn't
seem useful here.  (The elisp manual also says that sit-for will wait
for the specified amount of time or "until there is input
available"--it's not clear whether this includes output from
subprocesses, but there is already a call to accept-process-output
anyway...)

-- 
Gaute Strokkenes                        http://www.srcf.ucam.org/~gs234/
What a COINCIDENCE!  I'm an authorized ``SNOOTS OF THE STARS'' dealer!!



             reply	other threads:[~2003-07-14  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14  2:05 Gaute B Strokkenes [this message]
2003-07-14  7:45 ` Simon Josefsson
2003-07-14  8:21   ` Gaute B Strokkenes
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=87znjhsw0d.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).