Subject: bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode)

From: Stefan Kangas <[email-masked]>
Date: Mon, 10 Aug 2020 09:25:24 -0700

Stefan Monnier <[email-masked]> writes:

>> diff --git a/lisp/mouse.el b/lisp/mouse.el
>> index 5eeee1ec52..c165e1b0d2 100644
>> --- a/lisp/mouse.el
>> +++ b/lisp/mouse.el
>> @@ -1740,7 +1740,7 @@ mouse-drag-secondary
>>        (let (event end end-point)
>>  	(track-mouse
>>  	  (while (progn
>> -		   (setq event (read-event))
>> +		   (setq event (read-key))
>>  		   (or (mouse-movement-p event)
>>  		       (memq (car-safe event) '(switch-frame select-window))))
>>
>> Stefan, the above is what I meant by "is using `read-key' inside of
>> `track-mouse' an acceptable stopgap solution?".
>
> Yes, it's better than nothing.
> But maybe this can go to `master` since it's not an urgent matter, AFAIK.

(That was almost three years ago.)

This patch was never installed.  Is it still relevant?

Best regards,
Stefan Kangas