From: storm@cua.dk (Kim F. Storm)
Cc: storm@cua.dk, deego@gnufans.org, emacs-devel@gnu.org
Subject: Re: idledo.el v. 0.3
Date: 27 Oct 2002 00:51:19 +0200 [thread overview]
Message-ID: <5xbs5gddaw.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <E185XLK-0002R9-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> Add a new function:
>
> (timer-idle-timer-first-invocation-p TIMER)
>
> which allows an idle-timer action to check whether this is the first
> invocation of the timer after emacs becoming idle, or a repeated
> activation.
>
> Is there an actual need for this, or just a theoretical need? You
> could do it easily enough by setting a flag variable when the timer
> runs, and clearing it using timer-no-longer-idle-hook.
True, it is strictly not needed, since the hook can use a boolean to
know whether it was repeated (or activated at all)... However, since
that information which is already recorded in the timer vector, it
seemed natural (and friendly :-) to give the hook easy access to that
information.
>
> Add a new hooks:
>
> timer-no-longer-idle-hook
>
> [Implementation: Run from the above mentioned pre-command hook.]
>
> This is a useful feature, but why not use pre-command-hook directly?
Because the pre-command-hook is called for all command - also when
emacs hasn't been idle; that seems highly wasteful to me.
I'll make a patch for the proposed features; then you can see how much
of that you want me to install.
next prev parent reply other threads:[~2002-10-26 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wuobakqz.fsf@computer.localdomain>
[not found] ` <5xfzuyqbxo.fsf@kfs2.cua.dk>
[not found] ` <874rbduxdf.fsf@computer.localdomain>
[not found] ` <5xbs5ljj6s.fsf@kfs2.cua.dk>
[not found] ` <87u1jcq1ex.fsf@computer.localdomain>
2002-10-23 23:49 ` idledo.el v. 0.3 Kim F. Storm
2002-10-23 23:23 ` D. Goel
2002-10-23 23:51 ` D. Goel
2002-10-24 10:48 ` Kim F. Storm
2002-10-24 12:06 ` D. Goel
2002-10-24 15:05 ` Kim F. Storm
2002-10-24 14:25 ` D. Goel
2002-10-25 5:35 ` Richard Stallman
2002-10-25 5:34 ` Richard Stallman
2002-10-25 9:11 ` Kim F. Storm
2002-10-26 20:15 ` Richard Stallman
2002-10-26 22:51 ` Kim F. Storm [this message]
2002-10-28 19:19 ` Richard Stallman
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=5xbs5gddaw.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=deego@gnufans.org \
--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).