Re: Can we make set_point_both less expensive?

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden
> Date: Mon, 23 Mar 2015 15:28:53 -0400
> 
> > Otherwise, running the function before redisplay finished its job and
> > returned after marking the window up-to-day is bound to catch
> > incorrect position of point/cursor sometimes.
> 
> I'm completely lost.  What kind of "incorrect position" and what kind of
> "catching" are you worried about?

"Incorrect position" == position that will never be shown to the user.

"Catching" == using an incorrect position for the purposes discussed
in this thread.