From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark Plaksin Newsgroups: gmane.emacs.devel Subject: Re: Fwd: HTTP redirects make url-retrieve-synchronously asynchronous Date: Sun, 19 Feb 2006 15:15:18 -0500 Message-ID: References: <87y81ep6wf.fsf-monnier+emacs@gnu.org> <87wtgu8trl.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1140392258 17994 80.91.229.2 (19 Feb 2006 23:37:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 19 Feb 2006 23:37:38 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 20 00:37:37 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FAy7K-0006zH-AL for ged-emacs-devel@m.gmane.org; Mon, 20 Feb 2006 00:37:27 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FAy7J-0002Nh-TH for ged-emacs-devel@m.gmane.org; Sun, 19 Feb 2006 18:37:25 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FAuxy-0006RK-ET for emacs-devel@gnu.org; Sun, 19 Feb 2006 15:15:35 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FAuxr-0006PP-CC for emacs-devel@gnu.org; Sun, 19 Feb 2006 15:15:27 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FAuxp-0006Og-PJ for emacs-devel@gnu.org; Sun, 19 Feb 2006 15:15:25 -0500 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FAv3h-0001mB-Sy for emacs-devel@gnu.org; Sun, 19 Feb 2006 15:21:30 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FAuxn-000507-Hs for emacs-devel@gnu.org; Sun, 19 Feb 2006 21:15:23 +0100 Original-Received: from stone.tss.usg.edu ([168.24.82.77]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 19 Feb 2006 21:15:23 +0100 Original-Received: from happy by stone.tss.usg.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 19 Feb 2006 21:15:23 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 17 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: stone.tss.usg.edu User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.51 (gnu/linux) Cancel-Lock: sha1:3MoLP7ety/qrTKd1xXPqWy1aRTY= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:50773 Archived-At: Stefan Monnier writes: >>> 2. sometimes the callback gets called in another buffer than the one >>> returned by url-retrieve. > >>> One solution would be to give the first buffer a local variable that >>> would, in this case, point to the second buffer. >>> Then url-retrieve-synchronously could check the local variable, which >>> would tell it to check the process in the other buffer. > >> Yes, sounds like a good quick-fix. > > The patch below uses this approach. Mark, does it work well for you? It does; thanks! Are applications supposed to be aware of the possibility of redirect buffers and clean up both the original buffer and the redirect buffer? You could easily say "It's a work around, so yes!" :)