Re: Can we make set_point_both less expensive?

[Stefan Monnier]

>> > Another, related, requirement is that we never call
>> > pre-redisplay-function when point is in a position that is not
>> > supposed to be visible by the user.
>> Do you mean invisible text here?
> No, I mean positions traversed while "this command" is executed.  The
> position shown to the user is the last one of those, but how do we
> ensure that pre-redisplay-function is never run for those?

Ah, I see what you mean now: the command ensures this by not causing
redisplay during its execution.

Since pre-redisplay-function is run only at the beginning of redisplay,
it is only run when we're about to make the current state "visible by
the user".


        Stefan