From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: w3 under development or not? Date: Wed, 12 Nov 2003 13:59:40 GMT Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: <878ymm6d18.fsf@lucien.dreaming> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1068647028 14170 80.91.224.253 (12 Nov 2003 14:23:48 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 12 Nov 2003 14:23:48 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Nov 12 15:23:45 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AJvuL-0008Ds-00 for ; Wed, 12 Nov 2003 15:23:45 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AJwjo-0004H7-HS for geh-help-gnu-emacs@m.gmane.org; Wed, 12 Nov 2003 10:16:56 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!cyclone.bc.net!snoopy.risq.qc.ca!charlie.risq.qc.ca!53ab2750!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Original-NNTP-Posting-Host: 132.204.24.42 Original-X-Complaints-To: abuse@umontreal.ca Original-X-Trace: charlie.risq.qc.ca 1068645580 132.204.24.42 (Wed, 12 Nov 2003 08:59:40 EST) Original-NNTP-Posting-Date: Wed, 12 Nov 2003 08:59:40 EST Original-Xref: shelby.stanford.edu gnu.emacs.help:118162 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:14103 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:14103 > I think this discussion refers to the function url-retrieve-synchronously, > where the following piece of code can be found: > ;; Quoth monnier: > ;; 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. > ;; (sit-for 0.1) > (sleep-for 0.1)) > Your change did not resolve the problem completely, so I changed it to > (sit-for 0 250) followed by (discard-input). I am not sure if it is a That sounds interesting. Are you saying that you not only see hangs with my code but you also see hangs with the old code (in the only case I've heard of where someone had trouble with my version of the above code, that smeone also said that reverting my change fixed his problem). Maybe instead of discard-input we could do something like (while (input-pending-p) (push (read-event) w3-temp-read-events)) and then push those events back onto unread-command-events when the whole thing is done ? Still, it seems the problem is revealing a bug in the underlying C code, and it would be even better to fix that one. Stefan