From: Ship Mints <shipmints@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74833@debbugs.gnu.org, fgunbin@fastmail.fm
Subject: bug#74833: 31.0.50; Copy to OS clipboard doesn't work in macOS Terminal.app with xterm-mouse-mode enabled
Date: Thu, 12 Dec 2024 15:31:00 -0500 [thread overview]
Message-ID: <CAN+1HbrAA9HuGp-VFfQUbFLfu87B=2u6xYKs-=RR64p4Z7Ozfw@mail.gmail.com> (raw)
In-Reply-To: <86y10ky9wf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
I have xterm-mouse-mode enabled when in tty mode on macOS and it does work
for clicking/selecting but this is independent of integrating the kill ring
with the pasteboard. I am unaware of how to test the completeness of the
xterm mouse protocol support, however.
On Thu, Dec 12, 2024 at 2:32 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Ship Mints <shipmints@gmail.com>
> > Date: Thu, 12 Dec 2024 14:18:47 -0500
> > Cc: Filipp Gunbin <fgunbin@fastmail.fm>, 74833@debbugs.gnu.org
> >
> > It supports a subset of mouse behavior via this user setting:
> >
> >
> https://support.apple.com/guide/terminal/turn-on-mouse-reporting-trmlc69728a5/2.12/mac/11.0
>
> That doesn't tell enough. xterm.el and xterm-mouse assume full
> support for the xterm protocols, so partial support could well explain
> why things don't work.
>
> In general, I don't recommend turn on xterm features on terminals
> other than xterm, unless they are faithful emulations of xterm.
>
[-- Attachment #2: Type: text/html, Size: 1721 bytes --]
next prev parent reply other threads:[~2024-12-12 20:31 UTC|newest]
Thread overview: 10+ 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 [this message]
2024-12-12 19:55 ` Gerd Möllmann
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='CAN+1HbrAA9HuGp-VFfQUbFLfu87B=2u6xYKs-=RR64p4Z7Ozfw@mail.gmail.com' \
--to=shipmints@gmail.com \
--cc=74833@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fgunbin@fastmail.fm \
/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).