From: Nick Roberts <nickrob@snap.net.nz>
Subject: post-command-idle-hook
Date: Mon, 16 May 2005 09:32:36 +1200 [thread overview]
Message-ID: <17031.49140.784687.317291@farnswood.snap.net.nz> (raw)
TODO has the following item:
* Small but important fixes needed in existing features:
** Convert everything that uses post-command-idle-hook
to use idle timers instead.
I can only find two reference to post-command-idle-hook:
1) speedbar.el which, in any case, uses which uses run-with-idle-timer when
there is no binding for post-command-idle-hook.
2) follow.el which only seems to use post-command-idle-hook to cover the
case where another function is already on post-command-idle-hook.
Would it be a good idea now to remove post-command-idle-hook from Emacs
and its reference in follow.el?
Nick
next reply other threads:[~2005-05-15 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 21:32 Nick Roberts [this message]
2005-05-18 22:45 ` post-command-idle-hook Richard Stallman
2005-05-18 23:59 ` post-command-idle-hook Nick Roberts
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=17031.49140.784687.317291@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
/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).