From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: url.el blocks Gnus+nnrss
Date: Thu, 13 Jan 2005 21:16:19 +0900 [thread overview]
Message-ID: <b9yy8explrg.fsf@jpl.org> (raw)
Hi,
Several people reported that Gnus hangs if they subscribe to
nnrss groups. nnrss is a back end which uses the url ELisp
package by default and enables to read rss feeds as if they were
newsgroups.
When starting Gnus or typing `g' (gnus-group-get-new-news), it
gets into the infinite loop. The reason the problem arises is
stated in the `url-retrieve-synchronously' section of the url.el
file as follows:
;; Quoth Stef:
;; It turns out that the problem seems to be that the (sit-for
;; 0.1) below doesn't actually process the data: instead it
;; returns immediately because there is keyboard input
;; waiting, so we end up spinning endlessly waiting for the
;; process to finish while not letting it finish.
;; However, raman claims that it blocks Emacs with Emacspeak
;; for unexplained reasons. Put back for his benefit until
;; someone can understand it.
;; (sleep-for 0.1)
(sit-for 0.1))
I don't know why it sticks to `sleep-for' or `sit-for'.
Although both process data, there are adverse effects as the
comment mentioned. Isn't the function which should process data
from the network `accept-process-output'? I tried it there and
confirmed it solves the problem. Since I don't have Emacspeak,
I'm not sure whether it doesn't trouble Emacspeak users, though.
The patch is here:
*** url.el~ Sun Nov 21 22:23:54 2004
--- url.el Thu Jan 13 12:15:19 2005
***************
*** 177,194 ****
(while (not retrieval-done)
(url-debug 'retrieval "Spinning in url-retrieve-synchronously: %S (%S)"
retrieval-done asynch-buffer)
! ;; Quoth Stef:
! ;; It turns out that the problem seems to be that the (sit-for
! ;; 0.1) below doesn't actually process the data: instead it
! ;; returns immediately because there is keyboard input
! ;; waiting, so we end up spinning endlessly waiting for the
! ;; process to finish while not letting it finish.
!
! ;; However, raman claims that it blocks Emacs with Emacspeak
! ;; for unexplained reasons. Put back for his benefit until
! ;; someone can understand it.
! ;; (sleep-for 0.1)
! (sit-for 0.1))
asynch-buffer)))
(defun url-mm-callback (&rest ignored)
--- 177,183 ----
(while (not retrieval-done)
(url-debug 'retrieval "Spinning in url-retrieve-synchronously: %S (%S)"
retrieval-done asynch-buffer)
! (accept-process-output (get-buffer-process asynch-buffer) 0 100000 1))
asynch-buffer)))
(defun url-mm-callback (&rest ignored)
next reply other threads:[~2005-01-13 12:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 12:16 Katsumi Yamaoka [this message]
2005-01-13 14:35 ` url.el blocks Gnus+nnrss Stefan Monnier
2005-01-13 22:39 ` Katsumi Yamaoka
2005-01-25 14:32 ` Klaus Straubinger
2005-01-25 16:51 ` Stefan Monnier
2005-01-26 15:02 ` Klaus Straubinger
2005-01-28 16:58 ` Stefan Monnier
2005-02-01 9:35 ` Klaus Straubinger
2005-01-28 23:16 ` Dave Love
2005-01-29 16:21 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9yy8explrg.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).