comparison lisp/url/url.el @ 83290:042f282a2ed7

Merged from [e-mail]--gnu-2005 (patch 66, 266-268) Patches applied: * [e-mail]--gnu-2005/emacs--cvs-trunk--0--patch-266 Update from CVS * [e-mail]--gnu-2005/emacs--cvs-trunk--0--patch-267 Update from CVS * [e-mail]--gnu-2005/emacs--cvs-trunk--0--patch-268 Merge from gnus--rel--5.10 * [e-mail]--gnu-2005/gnus--rel--5.10--patch-66 Update from CVS git-archimport-id: [e-mail]--2004/emacs--multi-tty--0--patch-330

83289:1e53ee7473e9

	  nil
	(while (not retrieval-done)
	  (url-debug 'retrieval
		     "Spinning in url-retrieve-synchronously: %S (%S)"
		     retrieval-done asynch-buffer)
	  ;; We used to use `sit-for' here, but in some cases it wouldn't
	  ;; work because apparently pending keyboard input would always
	  ;; interrupt it before it got a chance to handle process input.
	  ;; `sleep-for' was tried but it lead to other forms of
	  ;; hanging.  --Stef
	  (unless (accept-process-output proc)
	    ;; accept-process-output returned nil, maybe because the process
	    ;; exited (and may have been replaced with another).
	    (setq proc (get-buffer-process asynch-buffer)))))
      asynch-buffer)))

(defun url-mm-callback (&rest ignored)
  (let ((handle (mm-dissect-buffer t)))
    (save-excursion

83290:042f282a2ed7

	  nil
	(while (not retrieval-done)
	  (url-debug 'retrieval
		     "Spinning in url-retrieve-synchronously: %S (%S)"
		     retrieval-done asynch-buffer)
	  (if (memq (process-status proc) '(closed exit signal failed))
	      ;; FIXME: It's not clear whether url-retrieve's callback is
	      ;; guaranteed to be called or not.  It seems that url-http
	      ;; decides sometimes consciously not to call it, so it's not
	      ;; clear that it's a bug, but even if we need to decide how
	      ;; url-http can then warn us that the download has completed.
              ;; In the mean time, we use this here workaround.
              (setq retrieval-done t)
            ;; We used to use `sit-for' here, but in some cases it wouldn't
            ;; work because apparently pending keyboard input would always
            ;; interrupt it before it got a chance to handle process input.
            ;; `sleep-for' was tried but it lead to other forms of
            ;; hanging.  --Stef
            (unless (accept-process-output proc)
              ;; accept-process-output returned nil, maybe because the process
              ;; exited (and may have been replaced with another).
              (setq proc (get-buffer-process asynch-buffer))))))
      asynch-buffer)))

(defun url-mm-callback (&rest ignored)
  (let ((handle (mm-dissect-buffer t)))
    (save-excursion