From: Eli Zaretskii <eliz@gnu.org>
To: "Francesco Potortì" <Potorti@isti.cnr.it>
Cc: 73469@debbugs.gnu.org
Subject: bug#73469: 29.4; mouse passing on terminal window generates events
Date: Wed, 25 Sep 2024 18:45:23 +0300 [thread overview]
Message-ID: <861q17d9f0.fsf@gnu.org> (raw)
In-Reply-To: <E1stR3J-00000009Csd-0hCq@tucano.isti.cnr.it> (bug-gnu-emacs@gnu.org)
> Date: Wed, 25 Sep 2024 14:23:29 +0200
> From: Francesco Potortì via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> I don't know when this has started happening. I use the Emacs shipped
> by Debian, so I suppose it started when Debian pushed a new version
> into Testing.
What was the previous Emacs version you used?
> I run Lucid Emacs inside Screen, running in a Mate-Terminal window under
> the Mate desktop under X.
>
> From the terminal emacs frame, I create X frames and usually work there,
> when I'm on X. However, I keep the terminal open and sometimes I use
> the emacs frame in the terminal.
>
> When the mouse cursor passes over the terminal window, it generates
> events, like this as seen by view-lossage:
>
> C-<mouse-1> 1 2 0 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 1 2 0 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 1 2 0 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 1 2 0 ; 2 1 M <switch-frame> ESC [ M 3 5 ; C-<mouse-1> 1 1 0 ; 2 2 M ESC [ M 3 5 ; C-<mouse-1> 1 0 4 ; 2 2 M ESC [ M 3 5 ; C-<mouse-1> 9 8 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 9 7 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 9 7 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 9 6 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 9 4 ; 2 1 M ESC [ M 3 5 ; C-<mouse-1> 9 0 ; 2 2 M ESC [ M 3 5 ; C-<mouse-1> 8 8 ; 2 2 M ESC [ M 3 5 ; C-<mouse-1> 8 7 ; 2 2 M ESC [ 2 1 ~ C-j ;; electric-newline-and-maybe-indent
> C-h l ;; view-lossage
>
> After passing the mouse over the windows, it almost always calls the terminal menu (in red and blue colors) and I have to hit f10 to make it go away. Often I do not realise that I have moved the mouse over the termial window and I find Emacs apparently hung on the X frames, until I go to the terminal window and hit f10. Sometimes Emacs hangs during one of these events and I have to kill it as I find no way to revive it.
>
> I do not know if this depends on mate-terminal, screen or emacs, and I have not tried to debug it, as I just discovered the reason why this happens at all (that is, passing the mouse cursor over the terminal window).
>
> If this is not a known bug, please let me know and I'll try to dig deeper. Suggestions at where to start looking at would be appreciated.
I'd start at the terminal-specific initializations your sessions are
loading. What does tty-type return when called without arguments from
the terminal Emacs frame?
The next suspect is xt-mouse.el.
Another thing to look into is whether this happens in "emacs -Q"; if
not, take a good look at your customizations, especially those which
are related to mouse support on terminal frames.
next prev parent reply other threads:[~2024-09-25 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 12:23 bug#73469: 29.4; mouse passing on terminal window generates events Francesco Potortì via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-25 15:45 ` Eli Zaretskii [this message]
2024-09-27 7:48 ` Francesco Potortì via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-27 10:25 ` Eli Zaretskii
2024-09-28 17:50 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-29 8:52 ` Francesco Potortì via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-29 19:10 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-29 20:07 ` Francesco Potortì via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-05 15:15 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-19 7:04 ` Eli Zaretskii
2024-10-19 8:24 ` Francesco Potortì 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=861q17d9f0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73469@debbugs.gnu.org \
--cc=Potorti@isti.cnr.it \
/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).