From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28658@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 [thread overview]
Message-ID: <87k205yrkv.fsf@gmail.com> (raw)
In-Reply-To: <831smgwwix.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Oct 2017 10:44:22 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex <agrambot@gmail.com>
>> Cc: 28658@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?
next prev parent reply other threads:[~2017-10-09 2:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 22:06 bug#28658: 27.0.50; [PATCH] double/triple clicking in xterm-mouse-mode doesn't respect mouse position Alex
2017-10-01 3:56 ` Alex
2017-10-01 8:23 ` martin rudalics
2017-10-01 18:30 ` Alex
2017-10-05 10:52 ` Eli Zaretskii
2017-10-05 10:52 ` Eli Zaretskii
2017-10-06 0:03 ` Alex
2017-10-06 7:44 ` Eli Zaretskii
2017-10-09 2:37 ` Alex [this message]
2017-10-09 7:11 ` Eli Zaretskii
2017-10-05 10:36 ` Eli Zaretskii
2017-10-06 0:14 ` Alex
2017-10-06 7:14 ` Eli Zaretskii
2017-10-07 21:57 ` Alex
2017-10-08 7:42 ` Eli Zaretskii
2017-10-08 23:44 ` Alex
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k205yrkv.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=28658@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.