GNU bug report logs -
#25111
How modification-hooks let-bind inhibit-modification-hooks?
Previous Next
Full log
View this message in rfc822 format
Alan Mackenzie <acm <at> muc.de> writes:
> Hello, Eli and Noam (but mainly Noam).
>
> It's about time we finally got this matter tidied up, so...
Yeah, sorry I dropped the ball on this.
> I think the changes as now formulated are right. Perhaps one or both of
> you might like to give the following patch a quick review. Thanks!
Minor formatting nitpick:
> +++ b/doc/lispref/display.texi
> @@ -1752,9 +1752,12 @@ Overlay Properties
> +When these functions are called, @code{inhibit-modification-hooks} is
> +bound to non-@code{nil}. If the functions modify the buffer, you
> +might want to bind @code{inhibit-modification-hooks} to nil, so as to
^^^
> +cause the change hooks to run for these modifications. However, doing
> +this may call your own change hook recursively, so be sure to prepare
> +for that. @xref{Change Hooks}.
> +++ b/doc/lispref/text.texi
> @@ -3639,6 +3642,13 @@ Special Properties
> beginning and end of the inserted text. The functions are called
> @emph{after} the actual insertion takes place.
>
> +When these functions are called, @code{inhibit-modification-hooks} is
> +bound to non-@code{nil}. If the functions modify the buffer, you
> +might want to bind @code{inhibit-modification-hooks} to nil, so as to
^^^
@code{nil} for both of these, right? Otherwise looks good to me.
This bug report was last modified 6 years and 29 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.