From: Richard Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: mange@freemail.hu, disumu@x3y2z1.net, emacs-devel@gnu.org
Subject: Re: URL not following some 302 redirects after recent changes
Date: Fri, 02 Feb 2007 06:26:35 -0500 [thread overview]
Message-ID: <E1HCwYt-0006K1-M2@fencepost.gnu.org> (raw)
In-Reply-To: <87bqkek9s7.fsf@stupidchicken.com> (message from Chong Yidong on Wed, 31 Jan 2007 19:21:12 -0500)
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?
next prev parent reply other threads:[~2007-02-02 11:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 2:35 URL not following some 302 redirects after recent changes Diane Murray
2007-01-20 21:30 ` Chong Yidong
2007-01-22 6:04 ` Richard Stallman
2007-01-22 15:02 ` Stefan Monnier
2007-01-23 2:07 ` Richard Stallman
2007-01-24 16:05 ` Stefan Monnier
2007-02-12 1:37 ` T. V. Raman
2007-01-31 13:44 ` Diane Murray
2007-02-01 0:21 ` Chong Yidong
2007-02-02 11:26 ` Richard Stallman [this message]
2007-02-02 15:37 ` Stefan Monnier
2007-02-02 15:45 ` David Kastrup
2007-02-03 11:19 ` Richard Stallman
2007-02-03 11:42 ` David Kastrup
2007-02-03 11:19 ` Richard Stallman
2007-02-02 17:09 ` Chong Yidong
2007-02-03 11:19 ` Richard Stallman
2007-02-22 1:38 ` Kim F. Storm
2007-02-22 1:43 ` Chong Yidong
2007-02-22 9:26 ` Kim F. Storm
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=E1HCwYt-0006K1-M2@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=disumu@x3y2z1.net \
--cc=emacs-devel@gnu.org \
--cc=mange@freemail.hu \
/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).