From: Richard Stallman <rms@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: sit-for
Date: Thu, 03 Aug 2006 11:50:55 -0400 [thread overview]
Message-ID: <E1G8fTL-0002Xd-Hn@fencepost.gnu.org> (raw)
In-Reply-To: <m364hc3uqu.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
> Another possibility just occurred to me. Unlike the old sit-for, the
> new sit-for is not interrupted by input coming from processes (as
> opposed to user input). If gnus (or some other package) relies on
> this behavior, a bug will arise.
IMO, sit-for should never be interrupted by input coming from a
subprocess (that is what accept-process-output is for), and code
which relies on that behaviour is wrong.
Did the old sit-for really wake up when process input came in?
It was never supposed to -- that would have been a bug.
But I don't recall seeing any reports of such a bug.
The bug was that input events that did not correspond to any
real input could wake it up. But process output does not
work by generating input events.
prev parent reply other threads:[~2006-08-03 15:50 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 ` sit-for Chong Yidong
2006-08-02 6:06 ` sit-for David Kastrup
2006-08-03 15:50 ` Richard Stallman [this message]
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=E1G8fTL-0002Xd-Hn@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=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.