Re: Why have you disable mouse on TTY builds?

[Jared Finder]

> On Jan 18, 2025 at 11:34 AM, Angelo Graziosi <angelo.g0@libero.it> 
> wrote:
> Il 13/01/2025 07:36, Jared Finder ha scritto:
> > On 2025-01-08 22:25, Eli Zaretskii wrote:
> > > If MinTTY is not known to support OSC52, but actually does support
> > > that (does it?), perhaps we could add it to the known names?  Or does
> > > MinTTY not let us know its name programmatically?
> >
> > I don't know the state of MinTTY, I don't have access to it locally.
> > Angelo, can you please try running the following command in a bash 
> > shell
> > in MinTTY?
> >
> > echo -e '\e[>0q'
> >
> > Thanks.
> >
> > -- MJF
> In MinTTY it prints
>
> angelo@PC MSYS: ~
> $ echo -e '\e[>0q'
>
> angelo@PC MSYS: ~
> $ :>|mintty 3.7.7^[\

Looking at https://mintty.github.io/mintty.1.html, it appears that 
MinTTY does not enable OSC52 copy by default.  Does it have a sensible 
flow to inform the user how to enable OSC52 when it gets such a 
sequence?  Otherwise, I believe we should not enable xterm-mouse-mode by 
default on it.

The current pattern is that xterm-mouse-mode is only enabled by default 
when OSC52 copy and OSC52 or bracketed paste are both supported for a 
default configuration.  If copy requires customization, I think it's 
safe to assume such a user can also enable xterm-mouse-mode.

  -- MJF