unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: sit-for and idle timers
Date: Mon, 14 Aug 2006 14:34:49 -0400	[thread overview]
Message-ID: <871wrjkvxy.fsf@stupidchicken.com> (raw)
In-Reply-To: <20060811124841.840381.FMU5696@piglet.prv.splode.com> (Noah Friedman's message of "Fri, 11 Aug 2006 12:48:41 -0700 (PDT)")

Noah Friedman <friedman@splode.com> writes:

> The change to sit-for of 2006-07-26 ("Use new SECONDS arg of read-event
> instead of a timer") seems to cause problems with idle-timers
> which call sit-for.

This should now be fixed.

> Here's a small test case which demonstrates the problem:
>
>     (defvar itimer-test-wait 0.5)
>     (defvar itimer-test-depth 0)
>
>     (defun itimer-test ()
>       (setq itimer-test-depth (1+ itimer-test-depth))
>       (unwind-protect
>           (let ((flag nil))
>             (while (sit-for itimer-test-wait)
>               (setq flag (not flag))
>               (message "itimer-test-depth: %-3d%s"
>                        itimer-test-depth
>                        (if flag " (blink)" ""))))
>         (setq itimer-test-depth (1- itimer-test-depth))
>         (message "itimer-test-depth: %d" itimer-test-depth)))
>
>     (run-with-idle-timer 0.25 t 'itimer-test)
>
> In the pre-7/26 implementation, this timer should never print a depth
> greater than 1, and the "(blink)" text should blink on and off with a
> regular rhythm.

  parent reply	other threads:[~2006-08-14 18:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 19:48 sit-for and idle timers Noah Friedman
2006-08-11 21:00 ` Chong Yidong
2006-08-14 18:34 ` Chong Yidong [this message]
2006-08-14 19:20 ` Richard Stallman
2006-08-14 19:47   ` Chong Yidong
2006-08-14 20:05     ` Chong Yidong
2006-08-15 12:41       ` Richard Stallman
2006-08-15 20:12         ` Chong Yidong
2006-08-16 19:27           ` Richard Stallman
2006-08-16 19:38             ` Chong Yidong

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=871wrjkvxy.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 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).