[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25111:
From: |
Eli Zaretskii |
Subject: |
bug#25111: |
Date: |
Thu, 08 Dec 2016 17:55:09 +0200 |
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: 25111@debbugs.gnu.org
> Date: Wed, 07 Dec 2016 16:40:02 +0000
>
> I think that the first of these is incorrect. There is no need to bind
> `inhibit-modification-hooks' to `t'. More over, there may be reasons by
> bind `inhibit-modification-hooks' to `nil' (i.e. "If you do want
> modification hooks to be run...").
So if we envision that some hook will bind inhibit-modification-hooks
to nil, then that is the reason to bind it to t in a hokk which
doesn't want such hooks to be run.
> It possible that the documentation should say "Mostly, you should avoid
> modifying the buffer on these hooks, any other functionality using these
> modification-hooks will not be called."
You mean, not mention the variable at all? That'd be loss of useful
information, I think.
> The reason I ask all of this as a result of a concrete use
> case. yasnippet modifies the buffer in these hooks, in turn breaks my
> own package, lentic, which uses these hooks to respond to changes.
So how would you want the manual to help avert such calamities?
bug#25111: How modification-hooks let-bind inhibit-modification-hooks?, Noam Postavsky, 2016/12/05