[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: Daniel Colascione
Subject: Re: Can we make set_point_both less expensive?
Date: Mon, 16 Mar 2015 13:53:44 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0

On 03/16/2015 01:48 PM, Lennart Borgman wrote:
> On Mon, Mar 16, 2015 at 9:43 PM, Daniel Colascione <address@hidden> wrote:
>> modes should be using a
>> "level triggered" approach, where they inspect the current location of
>> point and update whatever state they need based on that current location.
> Don't they need the previous location sometimes too? (Entering
> direction in invisible regions, for example.)

We already have code to adjust point out of invisible regions. The
command loop takes care of that. AFAICT, the actual existing uses of
point motion hooks don't require state.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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