[Bug: 21.4.15] Extent after-change-functions bugs
jan at rychter.com
Fri Aug 13 17:17:18 EDT 2004
>>>>> "Marcus" == Marcus Harnisch <marcus.harnisch at gmx.net> writes:
Marcus> Hi Jan, There was some discussion about that on xemacs-design
Marcus> two years ago. The thread focusses on that issue around here:
Marcus> Besides, I had some private conversation with Hrvoje (same time
Marcus> frame), which indicated further issues with using the
Marcus> extent-property `after-change-functions'. Unfortunately I don't
Marcus> have these emails any more. Mabye Hrvoje does.
Marcus> IIRC, as far as the task I wanted to solve at the time was
Marcus> concerned, the extent-properties were not as efficient and had
Marcus> corner case issues. (Re)implementing them using buffer
Marcus> `after-change-functions' using, `map-extents' did the job quite
Well, I finally ended up doing the same thing (using the buffer
before-change-functions and after-change-functions). But this is a
workaround, not a real solution -- I still have this feeling that
extents could automate things for me much better, and that I'm just
using them as a kind of dumb, automatically growing regions.
Oh, well. Thanks for the information, anyway.
More information about the XEmacs-Beta