From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Nested sit-for's
Date: Wed, 16 Aug 2006 10:14:47 +0200 [thread overview]
Message-ID: <m3y7tp85c8.fsf_-_@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87y7tp90i1.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 15 Aug 2006 17:01:42 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
>> What about the change that we discussed where nested sit-for calls
>> should not wait longer than any of the outer calls??
>
> I haven't had a chance to spend much time on this project. One
> problem is that I haven't managed to find a simple test case that
> clearly demonstrates the old behavior is broken.
>
Try this evaluating this:
(defun st1 ()
(with-current-buffer (get-buffer-create "*st1*")
(goto-char (point-max))
(insert "<")
(sit-for 30)
(insert ">")))
(run-with-timer 1 2 'st1)
(progn
(message "sit-for...")
(sit-for 5)
(message "sit-for...done"))
Now, the sit-for...done message is shown after 30-35 seconds,
not after 5 seconds...
[repeat the last progn if you don't see the effect immediately]
The call to sit-for in the timer is probably "bad practice", but it
could just as well have happened in a process filter or some other
async handler.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next parent reply other threads:[~2006-08-16 8:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1GD2sr-0005PH-UP@savannah.gnu.org>
[not found] ` <m3bqqlka7e.fsf@kfs-l.imdomain.dk>
[not found] ` <87y7tp90i1.fsf@stupidchicken.com>
2006-08-16 8:14 ` Kim F. Storm [this message]
2006-08-16 19:08 ` Nested sit-for's Chong Yidong
2006-08-17 6:02 ` Richard Stallman
2006-08-17 11:15 ` Kim F. Storm
2006-08-17 14:02 ` David Kastrup
2006-08-18 15:47 ` Richard Stallman
2006-08-17 14:14 ` Chong Yidong
2006-08-17 15:09 ` Kim F. Storm
2006-08-17 17:21 ` Chong Yidong
2006-08-17 21:28 ` Kim F. Storm
2006-08-17 22:42 ` Chong Yidong
2006-08-17 16:05 ` martin rudalics
2006-08-17 21:33 ` Kim F. Storm
2006-08-18 9:03 ` martin rudalics
2006-08-18 9:26 ` Kim F. Storm
2006-08-20 13:54 ` Chong Yidong
2006-08-20 21:05 ` Kim F. Storm
2006-08-20 21:52 ` martin rudalics
2006-08-20 22:05 ` Kim F. Storm
2006-08-21 11:13 ` Richard Stallman
2006-08-21 11:45 ` Kim F. Storm
2006-08-21 16:14 ` Stefan Monnier
2006-08-21 17:18 ` martin rudalics
2006-08-22 1:40 ` Stefan Monnier
2006-08-22 7:42 ` Richard Stallman
2006-08-17 14:21 ` Chong Yidong
2006-08-18 15:47 ` Richard Stallman
2007-10-17 14:41 ` Juanma Barranquero
2007-10-18 5:02 ` Richard Stallman
2007-10-18 7:40 ` Juanma Barranquero
2007-10-23 7:13 ` Richard Stallman
2006-08-17 15:33 ` Drew Adams
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=m3y7tp85c8.fsf_-_@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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 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).