From: Ship Mints <shipmints@gmail.com>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: Eli Zaretskii <eliz@gnu.org>, 74833@debbugs.gnu.org
Subject: bug#74833: 31.0.50; Copy to OS clipboard doesn't work in macOS Terminal.app with xterm-mouse-mode enabled
Date: Fri, 13 Dec 2024 11:52:37 -0500 [thread overview]
Message-ID: <CAN+1Hbp8wuKb2PoLzLohOrWgs5pYJs3i+xTGaj+AaNwRZQG_pQ@mail.gmail.com> (raw)
In-Reply-To: <CAN+1Hbp52JGbEqJx9ogTeaJUWN_LoA_j+JNYg7oYGa1DWg9SkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3165 bytes --]
Try experimenting with alternative terminals such as
https://wezfurlong.org/wezterm/ which I've used and where I remap all of
the keys to pass through to Emacs vs. letting the terminal application
abscond with functions like Command-C. I can share my wezterm configuration
off line if you're interested. I still remain mostly GUI on macOS but
occasionally use the terminal, and especially useful for running Emacs via
ssh on a remote computer (vs. tramp).
On Fri, Dec 13, 2024 at 11:42 AM Ship Mints <shipmints@gmail.com> wrote:
> What you describe is normal behavior, even if it appears confusing. It's
> an "impedance mismatch" between terminal.app and being in a "curses"
> window. Terminal doesn't "see" selected text and hence Command-C is
> disabled. This is the opposite for a basic shell where terminal sees the
> text because it controls selection. You can see this by pulling down the
> Edit menu and seeing Copy grayed out. As far as how xterm-mouse-mode
> interferes with Command-C I'd have to disable it myself and see what's
> going on. Not sure how much value that adds, though. If you enable xclip,
> you'll get what you want being inside Emacs, after all, using M-w gets your
> selected text copied to the pasteboard.
>
> On Fri, Dec 13, 2024 at 11:35 AM Filipp Gunbin <fgunbin@fastmail.fm>
> wrote:
>
>> On 13/12/2024 09:21 +0200, Eli Zaretskii wrote:
>>
>> >> From: Ship Mints <shipmints@gmail.com>
>> >> Date: Thu, 12 Dec 2024 15:31:00 -0500
>> >> Cc: fgunbin@fastmail.fm, 74833@debbugs.gnu.org
>> >>
>> >> 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.
>> >
>> > So why is this an Emacs bug? It sounds like the OP expects something
>> > to happen which shouldn't, because the xterm protocol for selections
>> > and the clipboard are not supported by Terminal.app? In that case,
>> > this could be at best a feature request, not a bug.
>>
>> I'll try to explain differently.
>>
>> Without xterm-mouse-mode you can copy/paste from/into Terminal.app
>> window, looks like Terminal.app gives this ability on its own. This is
>> not integration with Emacs kill ring, no. Emacs cursor does not react
>> to mouse clicks, and selection happens with OS mouse pointer. Paste
>> works rather slow (bad idea to paste large chunks of text), but
>> tolerable.
>>
>> Now, yesterday my daily master build got me xterm-mouse-mode enabled, so
>> I did some testing just out of curiosity. Most of the things work,
>> including clicking and selection. However, Command-C now just doesn't
>> copy text to OS clipboard. And it's non-obvious that you should disable
>> xterm-mouse-mode to be able to copy.
>>
>> That's why I filed this bug - because previous behavior was not ideal
>> but working, and now only paste works.
>>
>> Maybe we should just avoid enabling xterm-mouse-mode in Terminal.app.
>> Maybe functionality of xclip should be in core.
>>
>
[-- Attachment #2: Type: text/html, Size: 4287 bytes --]
next prev parent reply other threads:[~2024-12-13 16:52 UTC|newest]
Thread overview: 19+ 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 [this message]
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-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+1Hbp8wuKb2PoLzLohOrWgs5pYJs3i+xTGaj+AaNwRZQG_pQ@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).