Re: Idleness

[Harald Meland <Harald.Meland@usit.uio.no>]

[Hrvoje Niksic]

| I think that:
| 
| 	* adding a new idle timer from the idle-timer callback
| 
| is less of a hack.  I wonder if it would work correctly?

I just did some simple testing, and it doesn't look like it would.  As
I noted in my previous mail, it appears that Emacs needs to go from a
non-idle state and remain idle for SECS seconds before FUNCTION is
called.

If you add an idle timer from the present idle timer FUNCTION, the new
FUNCTION will not get called before Emacs goes non-idle and then idle
again.

Of course you could add a non-idle timer, but this would have to check
whether Emacs has become non-idle every time it get's called, and I
can't find any way of determining that -- short of the present hack in
Gnus, and then we're back to square one, right?


BTW, here's the code I used for my testing.  Note that it will
positively break if the SECS argument used in the callback is larger
than the SECS argument in the separate `run-with-idle-timer' call, as
that would imply removing the spurious timer before it gets called.

(defvar harald-test-idle-timer-mother-timer nil)
(defvar harald-test-idle-timer-spurious-timer nil)

(defun harald-test-idle-timer-function ()
  (when harald-test-idle-timer-spurious-timer
    (cancel-timer harald-test-idle-timer-spurious-timer))
  (setq harald-test-idle-timer-spurious-timer
	(run-with-idle-timer 2 t 'harald-test-idle-timer-function))
  (message (current-time-string)))

(setq harald-test-idle-timer-mother-timer
      (run-with-idle-timer 5 t 'harald-test-idle-timer-function))
-- 
Harald