Re: nnimap hangs on connect plus Garbage:

[Mats Lidell <Mats.Lidell@contactor.se>]

>>>>> Simon wrote:

Simon> Does the following have any effect?

Simon> --- imap.el.~6.3.~	Wed Dec 20 18:14:16 2000
Simon> +++ imap.el	Tue Feb  6 00:20:04 2001
Simon> @@ -857,13 +857,16 @@
Simon>  	  imap-current-message nil
Simon>  	  imap-state 'initial
Simon>  	  imap-process (condition-case ()
Simon> +			   (sit-for 1)
Simon>  			   (funcall (nth 2 (assq imap-stream 
Simon>  						 imap-stream-alist))
Simon>  				    "imap" buffer imap-server imap-port)
Simon> +			   (sit-for 1)
Simon>  			 ((error quit) nil)))
Simon>      (when imap-process
Simon>        (set-process-filter imap-process 'imap-arrival-filter)
Simon>        (set-process-sentinel imap-process 'imap-sentinel)
Simon> +      (sit-for 1)
Simon>        (while (and (eq imap-state 'initial)
Simon>  		  (memq (process-status imap-process) '(open run)))
Simon>  	(message "Waiting for response from %s..." imap-server)

Doesn't work. Is condition-case supposed to work that way?

Anyway. I looked down the funcall way and found that it hangs in
imap-network-open: (My messages) (Good old debug by print you know)

      (while (and (memq (process-status process) '(open run))
		  (goto-char (point-min))
		  (message "imap-network-open 3")
		  (not (imap-parse-greeting)))
	(accept-process-output process 1)
	(message "imap-network-open 4")
	(sit-for 1))

Endless sequence of "imap-network-open 3" and "imap-network-open 4"
seen in minibuffer.

When I break the loop with C-g the "*nnimap host" buffer contains a
valid greeting line. imap-parse-greeting returns t anyway.

Does this suggest that the "*nnimap host" buffer isn't updated so that
looking-at (in imap-parse-greeting) can see it? 

Removing the delay in accept-process-output stops Emacs completely
which suggests to me that all possible output was received but
imap-parse-greeting didn't see it.

Suggestions are welcome.

Yours
-- 
%% Mats