GNU bug report logs - #29150
26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode)

Previous Next

Package: emacs;

Reported by: Alex <agrambot <at> gmail.com>

Date: Sun, 5 Nov 2017 07:43:02 UTC

Severity: normal

Tags: patch

Found in version 26.0.90

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #62 received at 29150 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 29150 <at> debbugs.gnu.org,
 Olaf Rogalsky <olaf.rogalsky <at> t-online.de>, Alex <agrambot <at> gmail.com>
Subject: Re: bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in
 TTY (xterm-mouse-mode)
Date: Mon, 10 Aug 2020 09:25:24 -0700
Stefan Monnier <monnier <at> iro.umontreal.ca> 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




This bug report was last modified 4 years and 70 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.