From: Jared Finder <jared@finder.org>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Why have you disable mouse on TTY builds?
Date: Wed, 08 Jan 2025 20:54:44 -0800 [thread overview]
Message-ID: <d3e0afc78f418a17595aa7a2c1c2b217@finder.org> (raw)
In-Reply-To: <0d86c06f0409feb593245100b5282a19@finder.org>
On 2025-01-08 20:52, Jared Finder wrote:
> On 2025-01-08 08:15, Angelo Graziosi wrote:
>> Just for completeness,
>>
>> I tested also the last master on MinTTY which has
>>
>> $ echo $TERM
>> xterm
>>
>> but the mouse is not supported if I do not add these lines
>>
>> (require 'mouse)
>> (require 'mwheel)
>> (unless window-system
>> (xterm-mouse-mode t)
>> (mouse-wheel-mode t))
>>
>> to the init.el file.
>>
>> Is this to be expected?
>
> Yes, this is expected. MinTTY is not know to support OSC52 (copy /
> paste interaction with the OS), so the mouse is not automatically
> enabled.
>
> Note that I would expect you
Sorry, I mis-hit a key that sent this email early. :)
I meant to end with "note that I would expect you only need (unless
window-system (xterm-mouse-mode 1)). xterm-mouse-mode is autoloaded and
mouse-wheel-mode is enabled by default.
-- MJF
next prev parent reply other threads:[~2025-01-09 4:54 UTC|newest]
Thread overview: 16+ 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-08 16:15 ` Angelo Graziosi
2025-01-09 4:52 ` Jared Finder
2025-01-09 4:54 ` Jared Finder [this message]
2025-01-09 6:25 ` Eli Zaretskii
2025-01-09 8:04 ` Angelo Graziosi
2025-01-05 17:40 ` Angelo Graziosi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3e0afc78f418a17595aa7a2c1c2b217@finder.org \
--to=jared@finder.org \
--cc=angelo.g0@libero.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.