unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mark Kennedy <mark.t.kennedy@gmail.com>
Cc: 53353@debbugs.gnu.org
Subject: bug#53353: 29.0.50; spurious <tab-bar> <mouse-movement> events generated by mouse motion in tab-bar
Date: Wed, 19 Jan 2022 09:52:20 +0800	[thread overview]
Message-ID: <874k605w6j.fsf@yahoo.com> (raw)
In-Reply-To: <87bl08lepv.fsf@x1.mofjwutu.com> (Mark Kennedy's message of "Tue,  18 Jan 2022 20:02:52 -0500")

Mark Kennedy <mark.t.kennedy@gmail.com> writes:

> This bug occurs in LSP clients (observed for both scala and python) with
> many minor modes in effect.  Not feasible to reproduce from -Q.  Mouse motion in
> the tab bar (over both a tab name or the white space between them)
> generates unwanted "<tab-bar> <mouse-motion>" input events (which are
> unbound).

What is the value of `track-mouse' when the bug occurs?  Thanks.





  reply	other threads:[~2022-01-19  1:52 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874k605w6j.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53353@debbugs.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).