From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>, Jared Finder <jared@finder.org>
Cc: emacs-devel@gnu.org
Subject: Re: Why have you disable mouse on TTY builds?
Date: Sun, 05 Jan 2025 13:10:59 +0200 [thread overview]
Message-ID: <86msg58qik.fsf@gnu.org> (raw)
In-Reply-To: <6437ff4e-1594-426a-8502-f7a6bec82808@libero.it> (message from Angelo Graziosi on Sun, 5 Jan 2025 10:58:48 +0100)
> Date: Sun, 5 Jan 2025 10:58:48 +0100
> Cc: emacs-devel@gnu.org
> From: Angelo Graziosi <angelo.g0@libero.it>
>
>
>
> Il 05/01/2025 08:32, Eli Zaretskii ha scritto:
> >> Date: Sun, 5 Jan 2025 01:02:10 +0100
> >> From: Angelo Graziosi <angelo.g0@libero.it>
> >>
> >> Few weeks ago I built Emacs master for TTY om MSYS2 and without any
> >> settings in the init.el file Emacs and mouse worked on Windows Terminal.
> >> Few minutes ago I did another TTY build and mouse stopped to work. I had
> >> to read this
> >>
> >> (require 'mouse)
> >> (require 'mwheel)
> >> (unless window-system
> >> (xterm-mouse-mode t)
> >> (mouse-wheel-mode t))
> >>
> >> to the init.el..
> >>
> >> WHY?
> >
> > Which revision did you build? There were some changes lately
> > regarding xterm-mouse turned on by default, which could have affected
> > that, so it is important to know whether you build before or after
> > those changes.
>
> I built Emacs master after the mouse support was enable by default for
> TTY then have built Emacs master yesterday after the mouse support for
> TTY was disabled for a few terminals.
>
> In Windows Terminal the mouse support worked.
Can you tell more about the terminal you are using? How do you start
this terminal, and what program does it run?
Also, does it set TERM to some value, and if so, to which value?
> The real world is more complicated than the ideal world some
> programmer has in mind.
This is an unkind and unfair comment. We are trying to do our best,
but the number of terminals we know about is always finite, so there's
always some terminal we didn't know about.
Jared, can you please look into this?
next prev parent reply other threads:[~2025-01-05 11:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 0:02 Why have you disable mouse on TTY builds? Angelo Graziosi
2025-01-05 0:16 ` Angelo Graziosi
2025-01-05 9:05 ` Eli Zaretskii
2025-01-05 10:01 ` Angelo Graziosi
2025-01-05 7:32 ` Eli Zaretskii
2025-01-05 9:58 ` Angelo Graziosi
2025-01-05 11:10 ` Eli Zaretskii [this message]
2025-01-05 12:12 ` Angelo Graziosi
2025-01-05 16:53 ` Eli Zaretskii
2025-01-05 17:35 ` Jared Finder
2025-01-08 16:15 ` Angelo Graziosi
2025-01-09 4:52 ` Jared Finder
2025-01-09 4:54 ` Jared Finder
2025-01-09 6:25 ` Eli Zaretskii
2025-01-13 6:36 ` Jared Finder
2025-01-18 19:26 ` Angelo Graziosi
2025-01-09 8:04 ` Angelo Graziosi
2025-01-05 17:40 ` Angelo Graziosi
[not found] ` <f16cb443cd816ed73f31ba358654ac1e@finder.org 5c284702-c37e-47e2-95af-5db8f53e3ded@libero.it>
2025-01-19 4:54 ` Jared Finder
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=86msg58qik.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.g0@libero.it \
--cc=emacs-devel@gnu.org \
--cc=jared@finder.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).