From: Harald Meland <Harald.Meland@usit.uio.no>
Subject: Re: Idleness
Date: 17 Nov 1997 16:32:48 +0100 [thread overview]
Message-ID: <d6d4t5bsfhb.fsf@octarine.uio.no> (raw)
In-Reply-To: Hrvoje Niksic's message of "16 Nov 1997 03:06:59 +0100"
[Hrvoje Niksic]
| I noticed the code like this in gnus-util:
|
| (defun gnus-demon-is-idle-p ()
| "Whether Emacs is idle or not."
| ;; We do this simply by comparing the 100 most recent keystrokes
| ;; with the ones we had last time. If they are the same, one might
| ;; guess that Emacs is indeed idle. This only makes sense if one
| ;; calls this function seldom -- like once a minute, which is what
| ;; we do here.
| [...]
|
| Why use these hacks, instead of the standard XEmacs IS-IDLE argument
| to `start-itimer', or FSFmacs `run-with-idle-timer'? Not that the
| above hack doesn't work, but I just don't see the point...
|
| Is it a compatibility thing?
No, I guess it has to do with the gnus-demon functionality of running
a function every N minutes _after_ emacs has been idle for X minutes.
`run-with-idle-timer' will only let you run a function every time
Emacs has been idle for SECS seconds, so using this would merely move
the hacking elsewhere, not remove it.
I don't know if the way XEmacs provides idle timers would make the
removal of the hack easy.
--
Harald
next prev parent reply other threads:[~1997-11-17 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-16 2:06 Idleness Hrvoje Niksic
1997-11-17 15:32 ` Harald Meland [this message]
1997-11-17 18:37 ` Idleness Hrvoje Niksic
[not found] ` <x7hg9b70h7.fsf@peorth.gweep.net>
1997-11-17 21:41 ` Idleness Hrvoje Niksic
1997-11-17 22:40 ` Idleness Harald Meland
1997-11-17 23:05 ` Idleness Hrvoje Niksic
1997-11-18 2:46 ` Idleness Harald Meland
[not found] ` <x7n2j35dqa.fsf@peorth.gweep.net>
1997-11-17 23:51 ` Idleness Hrvoje Niksic
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=d6d4t5bsfhb.fsf@octarine.uio.no \
--to=harald.meland@usit.uio.no \
/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.
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 NNTP newsgroup(s).