From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: jared@finder.org, 74833@debbugs.gnu.org, fgunbin@fastmail.fm,
shipmints@gmail.com
Subject: bug#74833: 31.0.50; Copy to OS clipboard doesn't work in macOS Terminal.app with xterm-mouse-mode enabled
Date: Mon, 16 Dec 2024 19:42:35 +0200 [thread overview]
Message-ID: <86ldwfplro.fsf@gnu.org> (raw)
In-Reply-To: <m2jzbzfscp.fsf@gmail.com> (message from Gerd Möllmann on Mon, 16 Dec 2024 18:30:30 +0100)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Jared Finder <jared@finder.org>,
> 74833@debbugs.gnu.org, shipmints@gmail.com
> Date: Mon, 16 Dec 2024 18:30:30 +0100
>
> Mouse support by default is an important feature, IMO. It makes the menu
> bar usable, or in a future Emacs containing tty child frames tooltips
> can be shown. Not to mention setting point and what else.
I agree that mouse support is an important feature -- if it works well
and doesn't cause regressions. Here it seems like at least some
people could see some breakage.
It is easy to turn on xterm-mouse-mode for those who want it and don't
get anything broken due to it. Turning it on by default is only TRT
if there are no significant downsides. IOW, we shouldn't force users
to turn off some feature that is turned on by default because the
default doesn't work or breaks something.
So I still think it is safer to turn this off on Terminal.app, if we
can detect it.
next prev parent reply other threads:[~2024-12-16 17:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 17:54 bug#74833: 31.0.50; Copy to OS clipboard doesn't work in macOS Terminal.app with xterm-mouse-mode enabled Filipp Gunbin
2024-12-12 18:08 ` Ship Mints
2024-12-12 18:18 ` Filipp Gunbin
2024-12-12 18:20 ` Ship Mints
2024-12-12 19:15 ` Eli Zaretskii
2024-12-12 19:18 ` Ship Mints
2024-12-12 19:32 ` Eli Zaretskii
2024-12-12 20:07 ` Gerd Möllmann
2024-12-12 20:31 ` Ship Mints
2024-12-13 7:21 ` Eli Zaretskii
2024-12-13 14:46 ` Ship Mints
2024-12-13 16:35 ` Filipp Gunbin
2024-12-13 16:42 ` Ship Mints
2024-12-13 16:52 ` Ship Mints
2024-12-13 20:46 ` Filipp Gunbin
2024-12-13 16:49 ` Eli Zaretskii
2024-12-13 20:32 ` Filipp Gunbin
2024-12-13 20:54 ` Ship Mints
2024-12-14 7:52 ` Eli Zaretskii
2024-12-14 9:40 ` Gerd Möllmann
2024-12-16 16:32 ` Filipp Gunbin
2024-12-16 17:30 ` Gerd Möllmann
2024-12-16 17:42 ` Eli Zaretskii [this message]
2024-12-16 17:53 ` Gerd Möllmann
2024-12-16 19:09 ` Filipp Gunbin
2024-12-16 19:20 ` Ship Mints
2024-12-16 19:57 ` Gerd Möllmann
2024-12-16 19:58 ` Eli Zaretskii
2024-12-16 20:07 ` Ship Mints
2024-12-16 20:19 ` Eli Zaretskii
2024-12-16 19:53 ` Gerd Möllmann
2024-12-16 20:25 ` Filipp Gunbin
2024-12-16 20:29 ` Ship Mints
2024-12-12 19:55 ` Gerd Möllmann
2024-12-16 1:41 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 3:40 ` Gerd Möllmann
2024-12-16 5:16 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 16:37 ` Eli Zaretskii
2024-12-16 16:47 ` Ship Mints
2024-12-16 17:36 ` Gerd Möllmann
2024-12-16 16:30 ` Eli Zaretskii
2024-12-16 16:49 ` Filipp Gunbin
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=86ldwfplro.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74833@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=gerd.moellmann@gmail.com \
--cc=jared@finder.org \
--cc=shipmints@gmail.com \
/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).