Re: idledo.el v. 0.3

[Kim F. Storm]

Richard Stallman <address@hidden> 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.