The changed buffer turns out to be *code-conversion-work*, which is
a temporary buffer.
If you say: well, that buffer has changed at the point, and after-
change-functions are executed even for some internal, temporary
buffers, then I'll say: fair enough.
Yes.
_
> (add-hook 'after-change-functions 'yell-at-me)
Usually after-change-functions are only added buffer-locally, like this:
(add-hook 'after-change-functions 'yell-at-me nil t)
-- Stefan
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
On 6 Jun 2005, at 13:25, Richard Stallman wrote:
The hooks in after-change-functions seem to be called even when I
just open a menu from the menu bar with the mouse (before even
selecting a menu item!). Clearly, no change has been made to the
buffer in such a situation. I think t
The hooks in after-change-functions seem to be called even when I
just open a menu from the menu bar with the mouse (before even
selecting a menu item!). Clearly, no change has been made to the
buffer in such a situation. I think that after-change-functions
shouldn't be
> The hooks in after-change-functions seem to be called even when I just open
> a menu from the menu bar with the mouse (before even selecting a menu
> item!). Clearly, no change has been made to the buffer in such
> a situation. I think that after-change-functions shouldn't be called.
Testc
The hooks in after-change-functions seem to be called even when I
just open a menu from the menu bar with the mouse (before even
selecting a menu item!). Clearly, no change has been made to the
buffer in such a situation. I think that after-change-functions
shouldn't be called.
In GNU
