Re: Can we make set_point_both less expensive?

[Stefan Monnier]

>> >> what users of those features normally want is to catch movement of
>> >> the cursor
>> > You mean, we should do this in redisplay?
>> Probably in pre-redisplay-hook or in pre/post-command-hook, yes.
> That contradicts the "catch movement of cursor" idea: redisplay could
> well move point from where it is found before redisplay, as you know.

Indeed, that's a bug that we need to fix: after moving point, redisplay should
re-run pre-redisplay-hook; same thing after scrolling.


        Stefan