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

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alex <agrambot <at> gmail.com>
Cc: 28658 <at> debbugs.gnu.org
Subject: Re: bug#28658: 27.0.50;
 [PATCH] double/triple clicking in xterm-mouse-mode doesn't respect
 mouse position
Date: Fri, 06 Oct 2017 10:44:22 +0300

> From: Alex <agrambot <at> gmail.com>
> Cc: 28658 <at> debbugs.gnu.org
> Date: Thu, 05 Oct 2017 18:03:31 -0600
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> P.S. Why is the error prefixed by `xterm-mouse-translate-1' instead of
> >> `xterm-mouse-event'?
> >
> > Can you show the full backtrace?
> 
>   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.  Did you
look at the byte code?

Previous Next

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