all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: sit-for
Date: Tue, 01 Aug 2006 19:52:42 -0400	[thread overview]
Message-ID: <87mzaonhdh.fsf@stupidchicken.com> (raw)
In-Reply-To: <m364hc3uqu.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Wed, 02 Aug 2006 01:24:09 +0200")

>> Another possibility is to leave sit-for as it is, try to find code
>> that relies on sit-for returning due to process output, and fix it.
>
> Richard specifically asked [someone] to check all sit-for calls to see
> if the new behaviour would break them.  So [we] should already have
> done this (but I don't think anybody actually did that).

I did check, but maybe I missed something non-obvious.  The strange
behavior of Gnus reported by David Kastrup seems to indicate that some
code somewhere is relying on some undocumented feature of sit-for.

  reply	other threads:[~2006-08-01 23:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 21:06 sit-for David Kastrup
2006-07-28 21:48 ` sit-for Chong Yidong
2006-07-29  7:15   ` sit-for David Kastrup
2006-07-29  8:40     ` sit-for David Kastrup
2006-07-29 14:43       ` sit-for Chong Yidong
2006-07-30 22:36         ` sit-for Kim F. Storm
2006-07-31 18:29           ` sit-for Richard Stallman
2006-07-29 23:34       ` sit-for Richard Stallman
2006-07-29 23:34     ` sit-for Richard Stallman
2006-08-02  0:05     ` sit-for Chong Yidong
2006-08-02  6:09       ` sit-for David Kastrup
2006-08-01 16:38 ` sit-for Chong Yidong
2006-08-01 23:24   ` sit-for Kim F. Storm
2006-08-01 23:52     ` Chong Yidong [this message]
2006-08-02  6:06     ` sit-for David Kastrup
2006-08-03 15:50     ` sit-for 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mzaonhdh.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.