From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Q on after-change-functions
Date: Thu, 23 Feb 2006 10:50:23 -0500 [thread overview]
Message-ID: <87oe0y13jk.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.1173.1140573492.2856.help-gnu-emacs@gnu.org
> (set-buffer (window-buffer (minibuffer-window)))
> (add-hook 'after-change-functions 'foobar nil 'local)
The minibuffer's buffer is refreshed/recreated/reset every time you
enter it. Maybe it would work if you added (put 'after-change-functions
'permanent-local t), but that would be truly evil. Also it would still fail
in the case of recursive minibuffers where you may have several minibuffer
buffers active at the same time.
Instead, you want to do your `add-hook' from minibuffer-setup-hook.
See icomplete-mode for an example of a mode that does something similar
(tho it doesn't use after-change-functions but pre/post-command-hook
instead).
Stefan
next parent reply other threads:[~2006-02-23 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1173.1140573492.2856.help-gnu-emacs@gnu.org>
2006-02-23 15:50 ` Stefan Monnier [this message]
2006-02-22 1:57 Q on after-change-functions Drew Adams
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=87oe0y13jk.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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.
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).