Hrvoje Niksic writes:
Kyle Jones <kyle_jones(a)wonderworks.com> writes:
> Gunnar Evermann writes:
> > any suggestions for a fix?
>
> Modifications to the current buffer should be disallowed inside the
> before-/after- change functions, if we hope to have any consistency
> in the system.
This discussion sounds familiar. And again, I disagree with your
position. There are legitimate uses for changing the buffer from
within the before-/after- change functions, and custom has
demonstrated that.
Yeah, this discussion does sound familiar. I think my position
was "well, fix this broken code!" and no one else wanted to fix
it, so in order to implement the change I would have to fix it.
> We can fix the crash, but things like font-lock and setnu-mode,
> which rely on having access to every change to operate correctly,
> are still going to be screwed unless we disallow these changes.
Neither font-lock nor setnu are very useful with things like
Customize buffers.
Yes, but this is awfully ad hoc. We don't know what other
developers are going to do with the feature. It may be
imperative to see all the text that goes in and out of a
buffer, even in a Custom buffer. Change functions are very
low level, so it is important to keep things clean.
If I fix wid-edit.el (assuming its possible) and whatever else we
ship that uses buffer modifying change functions, would you be
more amenable to disabling buffer modifications while inside a
buffer change function?