From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: How to test whether any code runs after same command invocation?
Date: Fri, 14 Feb 2014 18:42:20 +0100 [thread overview]
Message-ID: <87lhxdioar.fsf@web.de> (raw)
In-Reply-To: jwvob29oc4f.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > I after-advice dired-insert-set-properties.
>
> Then why is the code run multiple times?
If you operate on several (marked) files, each file's line is refreshed
individually. Then the code is called several times (contrary to
e.g. just hitting g) after one command invocation.
> > I didn't want to cope with that. Also, this was just an example, I
> > have other, quite different use cases of the raised issue.
>
> The general idea might still apply: try and make it lazier. E.g. change
> your code so that rather than doing the job right away, it just writes
> down somewhere what jobs needs to be done, and then later (e.g. in
> post-command-hook, jit-lock, timer, you name it) look at what was
> written down (if anything) and do it then, once.
Indeed, that would be a much better approach, although this requires
some more effort.
> "Wall clock" is this thing that you can get from your watch, your
> phone,
I'm not so accustomed to such physical things...
> or the `current-time' function ;-)
Oh, that's what you meant, ok, I understand.
Many thanks, Stefan!
Michael.
next prev parent reply other threads:[~2014-02-14 17:42 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
2014-02-14 15:08 ` Michael Heerdegen
2014-02-14 17:15 ` Stefan Monnier
2014-02-14 17:42 ` Michael Heerdegen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhxdioar.fsf@web.de \
--to=michael_heerdegen@web.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.