From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: URL not following some 302 redirects after recent changes Date: Fri, 02 Feb 2007 06:26:35 -0500 Message-ID: References: <871wnw2opm.fsf@x3y2z1.net> <87tzy7wbsj.fsf@x3y2z1.net> <87bqkek9s7.fsf@stupidchicken.com> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1170415855 18396 80.91.229.12 (2 Feb 2007 11:30:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 2 Feb 2007 11:30:55 +0000 (UTC) Cc: mange@freemail.hu, disumu@x3y2z1.net, emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 02 12:30:45 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HCwcu-0003kM-MP for ged-emacs-devel@m.gmane.org; Fri, 02 Feb 2007 12:30:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HCwcu-0003Od-5d for ged-emacs-devel@m.gmane.org; Fri, 02 Feb 2007 06:30:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HCwcf-0003LV-BE for emacs-devel@gnu.org; Fri, 02 Feb 2007 06:30:29 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HCwce-0003KG-Hi for emacs-devel@gnu.org; Fri, 02 Feb 2007 06:30:28 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HCwcd-0003Jm-GR for emacs-devel@gnu.org; Fri, 02 Feb 2007 06:30:27 -0500 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HCwcW-0004ct-Vf for emacs-devel@gnu.org; Fri, 02 Feb 2007 06:30:22 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1HCwYt-0006K1-M2; Fri, 02 Feb 2007 06:26:35 -0500 In-reply-to: <87bqkek9s7.fsf@stupidchicken.com> (message from Chong Yidong on Wed, 31 Jan 2007 19:21:12 -0500) X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:65763 Archived-At: While a sentinel is running, the process sentinel is temporarily set to @code{nil} so that the sentinel won't run recursively. For this reason it is not possible for a sentinel to specify a new sentinel. We did that to avoid a class of bugs. But it has caused a new problem. So I am looking for a better solution. Here's one idea. Instead of setting the sentinel temporarily to nil, set it temporarily to `sentinel-temporarily-inhibited'. That would be ignored just as nil is ignored. On restoring the sentinel, if its current value isn't `sentinel-temporarily-inhibited', just discard the old value instead of restoring it. This would prevent recursion just like the current code, but sentinels that set the sentinel would work once again. Does anyone see a problem with this fix?