GNU bug report logs - #28658
27.0.50; [PATCH] double/triple clicking in xterm-mouse-mode doesn't respect mouse position

Previous Next

Full log

View this message in rfc822 format

From: Alex <agrambot <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 28658 <at> debbugs.gnu.org
Subject: bug#28658: 27.0.50; [PATCH] double/triple clicking in xterm-mouse-mode doesn't respect mouse position
Date: Sun, 08 Oct 2017 20:37:20 -0600

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Alex <agrambot <at> gmail.com>
>> Cc: 28658 <at> debbugs.gnu.org
>> Date: Thu, 05 Oct 2017 18:03:31 -0600
>> 
>>   Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>>     xterm-mouse-event(1006)
>>     xterm-mouse-translate-1(1006)
>>     xterm-mouse-translate-extended(nil)
>> 
>> So the backtrace acknowledges xterm-mouse-event is the culprit, but
>> without `debug-on-error' set the error message blames
>> xterm-mouse-translate-1.
>> 
>> If I don't use the bytecode versions of the procedures, though, then the
>> error message becomes:
>> 
>>   setq: Wrong type argument: number-or-marker-p, nil
>
> So this is something related to the byte compiler, I presume.

For the most part, yeah. Though without the byte compiler the error
message is prefixed by `setq' instead of `1+' as it should be (and is
when debugging).

> Did you look at the byte code?

No, I'm not sure what I should be looking for. I thought perhaps this
was a known limitation; should I report this as a bug?

Previous Next

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