On 03/16/2015 01:48 PM, Lennart Borgman wrote:
> On Mon, Mar 16, 2015 at 9:43 PM, Daniel Colascione <dancol@dancol.org> 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.