From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 53353@debbugs.gnu.org, mark.t.kennedy@gmail.com
Subject: bug#53353: 29.0.50; spurious <tab-bar> <mouse-movement> events generated by mouse motion in tab-bar
Date: Wed, 19 Jan 2022 17:31:07 +0800 [thread overview]
Message-ID: <87fspk3wdg.fsf@yahoo.com> (raw)
In-Reply-To: <83ilugtb5z.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 19 Jan 2022 09:52:24 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> The usual protocol is that Lisp programs that enable mouse tracking
> are those that bind mouse-movement events to 'ignore' as they see
> fit. If that is what you propose, then it follows that LSP should do
> that if it doesn't want to support mouse-movement on the tab bar.
bindings.el binds mouse-movement events to `ignore', so I think the same
should be done with the tab bar (and tool bar) mouse-movement events.
But either way, this is probably not a bug in Emacs. Mark, can you
verify whether or not `track-mouse' is not nil when those spurious
events are generated? Thanks.
next prev parent reply other threads:[~2022-01-19 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 1:02 bug#53353: 29.0.50; spurious <tab-bar> <mouse-movement> events generated by mouse motion in tab-bar Mark Kennedy
2022-01-19 1:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-19 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-19 7:52 ` Eli Zaretskii
2022-01-19 9:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-19 11:37 ` Eli Zaretskii
2022-01-19 11:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <CANru7VFRPt_To+v6PYCBBRbXVSQaXVWJsf-EK6WxPTXJvQuuiQ@mail.gmail.com>
2022-01-20 0:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87fspk3wdg.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=53353@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mark.t.kennedy@gmail.com \
/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.