Re: mouse-drag-and-drop-region

[Eli Zaretskii]

> Date: Fri, 24 Nov 2017 10:41:12 +0100
> From: martin rudalics <address@hidden>
> CC: address@hidden, address@hidden
> 
>  > Why would it be unsafe wrt redisplay?
> 
> Because of that part of tracking_off:
> 
>        /* Redisplay may have been preempted because there was input
>        available, and it assumes it will be called again after the
>        input has been processed.  If the only input available was
>        the sort that we have just disabled, then we need to call
>        redisplay.  */
>        if (!readable_events (READABLE_EVENTS_DO_TIMERS_NOW))
>       {
>         redisplay_preserve_echo_area (6);
>         get_input_pending (READABLE_EVENTS_DO_TIMERS_NOW);
>       }

With redisplay-dont-pause being t by default, this shouldn't happen
unless someone customizes that option.

> IIUC we don't do that in `mouse-drag-track'.

Why should we?  mouse-drag-track works via the normal command loop
machinery.