From: Eli Zaretskii <eliz@gnu.org>
To: Jared Finder <jared@finder.org>
Cc: 43756@debbugs.gnu.org, larsi@gnus.org
Subject: bug#43756: Fix for TTY menus mouse interaction
Date: Fri, 02 Oct 2020 22:35:55 +0300 [thread overview]
Message-ID: <83k0w8e7z8.fsf@gnu.org> (raw)
In-Reply-To: <3d6b6e0f894ab59c3b0df9394182f498@finder.org> (bug-gnu-emacs@gnu.org)
> Cc: 43756@debbugs.gnu.org
> Date: Fri, 02 Oct 2020 09:45:33 -0700
> From: Jared Finder via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> * Emacs repo from git://git.sv.gnu.org/emacs.git, commit
> f6277911eb2c520aec8f0efd80c91999226e3322
> * Run on Debian under Windows Subsystem for Linux 2 (the VM version).
> I've also seen this on MacOS and native Win32 builds of Emacs.
Native Windows build doesn't support xterm-mouse, and the native mouse
clicks work correctly there. If you have a recipe for the native
Windows build that shows incorrect menus popping down, please show
that.
> emacs -Q
> M-x ielm
> M-x xterm-mouse-mode
Ah, xterm-mouse-mode. AFAIR, no one has made TTY menus work with
xterm-mouse-mode. The first thing to do is to disable tmm-menubar,
and then you need to cause a mouse click call menu-bar-open with the
2nd argument set to the X coordinate of the click.
next prev parent reply other threads:[~2020-10-02 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 5:56 bug#43756: Fix for TTY menus mouse interaction Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 14:37 ` Lars Ingebrigtsen
2020-10-02 16:45 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 19:35 ` Eli Zaretskii [this message]
2020-10-02 19:54 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-03 7:23 ` Eli Zaretskii
2020-10-03 17:44 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-05 8:24 ` Lars Ingebrigtsen
2020-10-05 14:53 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-05 15:03 ` Eli Zaretskii
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=83k0w8e7z8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43756@debbugs.gnu.org \
--cc=jared@finder.org \
--cc=larsi@gnus.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 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).