[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can we make set_point_both less expensive?

From: Eli Zaretskii
Subject: Re: Can we make set_point_both less expensive?
Date: Fri, 20 Mar 2015 17:08:56 +0200

> Date: Fri, 20 Mar 2015 15:48:21 +0100
> From: martin rudalics <address@hidden>
> CC: Eli Zaretskii <address@hidden>, address@hidden, address@hidden
>  > Implement a new `cursor-intangible' property, by having p-r-f move point
>  > away from text with that property.
> Strictly spoken I see no reason why the display engine should not handle
> that property by itself.

Redisplay never moves point, except when it was forced to keep a
specific window-start position.  In all other cases, it scrolls the
display, but leave point intact.

And cursor is always set where point is, we have no other strategy for
positioning the cursor.  So I don't see how handling intangible could
be the job of redisplay, without significant changes.

> Someone would have to handle the scroll margins too when determining
> on which side of the area to move point.

Scroll margins don't cause point movement; they cause movement of text
wrt the window.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]