unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: How to test whether any code runs after same command invocation?
Date: Fri, 14 Feb 2014 09:27:30 -0500	[thread overview]
Message-ID: <jwv4n41zsag.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87eh36kl1f.fsf@web.de> (Michael Heerdegen's message of "Fri, 14 Feb 2014 12:09:48 +0100")

> Example: I use some code that propertizes any dired buffer in a way that
> the mouse tooltip over any directory shows the directory contents.
> Since that can take a long time for huge directory hierarchies, I want
> to use a timeout.  But if you have marked files you operate on, the code
> is run multiple times when refreshing the files' lines, so the timeout

Not sure I understand.  Do you use after-change-functions, by any chance?
Could you use jit-lock instead?

> I currently do this by (defvar counter 0) and adding a fun to
> post-command-hook that increases the counter.

That sounds like the standard hack, yes.

> Is there a cleverer way?

In general, not that I know.
You can also use wall-time instead of a counter incremented in
post-command-hook.


        Stefan



  reply	other threads:[~2014-02-14 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 11:09 How to test whether any code runs after same command invocation? Michael Heerdegen
2014-02-14 14:27 ` Stefan Monnier [this message]
2014-02-14 15:08   ` Michael Heerdegen
2014-02-14 17:15     ` Stefan Monnier
2014-02-14 17:42       ` Michael Heerdegen
2014-02-14 20:55         ` Stefan Monnier
2014-02-15 10:46           ` Michael Heerdegen
2014-02-14 18:41       ` Thien-Thi Nguyen
2014-02-15 10:36         ` Michael Heerdegen
2014-02-15 12:25           ` Thien-Thi Nguyen

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=jwv4n41zsag.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).