Re: Can we make set_point_both less expensive?

[Lennart Borgman <lennart.borgman@gmail.com>]

On Fri, Mar 20, 2015 at 3:14 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>
> For me, a bad interaction is one where p-r-f followed by redisplay
> followed by p-r-f followed by redisplay doesn't give the right answer.
>
> But with something like `cursor-intangible', there will surely be cases
> where that can happen.  E.g. imagine you scroll to a part of the buffer
> that's got a cursor-intangible element: redisplay will move point to
> a visible (and intangible) part of the buffer, then run p-r-f which
> moves point outside of the window, after which redisplay has two
> choices: either it decides to scroll to where point is (which would be
> wrong, since we've just scrolled so we should move point rather than
> scroll), or it moves point back into the intangible element.

Unless the functions in the hooks continues to change the display this
can't loop, or can it?