From: Angelo Graziosi <angelo.g0@libero.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jared@finder.org, emacs-devel@gnu.org
Subject: Re: Why have you disable mouse on TTY builds?
Date: Sun, 5 Jan 2025 18:40:41 +0100 [thread overview]
Message-ID: <8532a550-cd9b-47fa-8c6f-e2d4caf8723f@libero.it> (raw)
In-Reply-To: <86sepx6w2l.fsf@gnu.org>
Il 05/01/2025 17:53, Eli Zaretskii ha scritto:
> So I guess this terminal somehow doesn't pass this test in xterm.el:
>
> ;; Only automatically enable xterm mouse on terminals
> ;; confirmed to still support all critical editing
> ;; workflows (bug#74833).
> (or (string-match-p xterm--auto-xt-mouse-allowed-types
> (tty-type (selected-frame)))
> (and-let* ((name-and-version (xterm--query-name-and-version)))
> (string-match-p xterm--auto-xt-mouse-allowed-names
> name-and-version))))
>
> It is strange that you have TERM set to xterm-256color, though. I use
> the same Windows Terminal, both with cmd.exe and with MSYS Bash, and I
> don't see this value in any of them. What shell do you run inside the
> terminal? Are you sure this setting of TERM is not something your
> shell init files do? Or maybe you use WSL or something?
I use bash. WT is configured in settings.json as
"colorScheme": "MSYS2-Theme",
"commandline": "C:/msys64/usr/bin/bash --login",
"environment":
{
"CHERE_INVOKING": "1",
"MSYS": "winsymlinks:nativestrict",
"MSYS2_PATH_TYPE": "inherit",
"MSYSTEM": "MSYS"
},
"guid": "{fc173dff-fd24-43df-b40e-28853998c744}",
"icon": "C:/msys64/msys2.ico",
"name": "MSYS2 MSYS Shell",
"startingDirectory": "C:/msys64/home/%USERNAME%"
...
In MSYS, UCRT64 and WSL, TERM has the same value xterm-256color. I
grepped TERM in all .bashrc etc configuration files (also in /etc) but
the result is empty.
MinTTY set TERM to xterm. If I start MinTTY (TERM==xterm) and there I
type wsl to start WSL then even WSLstarted this way has TERM==xterm-256color
In short I did not find wher WT takes that value for TERM..
prev parent reply other threads:[~2025-01-05 17:40 UTC|newest]
Thread overview: 11+ 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
2025-01-05 12:12 ` Angelo Graziosi
2025-01-05 16:53 ` Eli Zaretskii
2025-01-05 17:35 ` Jared Finder
2025-01-05 17:40 ` Angelo Graziosi [this message]
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=8532a550-cd9b-47fa-8c6f-e2d4caf8723f@libero.it \
--to=angelo.g0@libero.it \
--cc=eliz@gnu.org \
--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).