From: Ship Mints <shipmints@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, fgunbin@fastmail.fm,
74833@debbugs.gnu.org, jared@finder.org, rms@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: Mon, 23 Dec 2024 14:36:34 +0100 [thread overview]
Message-ID: <CAN+1Hbp5MACbrKo3KTo5G0CXDo0v3kwSxes=Z3ZfJLsp-QB5Qg@mail.gmail.com> (raw)
In-Reply-To: <861pxy5zxk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
You should be able to paste using the (annoying, yes) CUA key Shift-Ins vs.
right mouse button.
I think the only way to know for sure you're under putty is to change your
putty configuration to set/send a custom environment variable that you can
test. I do not recall one that it sets/sends by default beyond TERM which
is "xterm" and that's obviously insufficient.
On Mon, Dec 23, 2024 at 1:47 PM Eli Zaretskii <eliz@gnu.org> wrote:
> I found one more case where turning on xterm-mouse-mode by default
> causes problems: PuTTY. It loses the ability to paste from the
> Windows clipboard by a right mouse click when xterm-mouse-mode is
> turned on.
>
> Can we identify PuTTY in some way, so that xterm-mouse-mode could not
> be turned on in that case?
>
[-- Attachment #2: Type: text/html, Size: 1284 bytes --]
next prev parent reply other threads:[~2024-12-23 13:36 UTC|newest]
Thread overview: 56+ 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
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-17 3:32 ` Gerd Möllmann
2024-12-17 12:32 ` Eli Zaretskii
2024-12-18 17:50 ` Ship Mints
2024-12-19 5:16 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 17:23 ` Ship Mints
2024-12-20 18:48 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-22 4:49 ` Richard Stallman
2024-12-22 6:12 ` Gerd Möllmann
2024-12-22 7:46 ` Eli Zaretskii
[not found] ` <861pxy5zxk.fsf@gnu.org>
2024-12-23 13:36 ` Ship Mints [this message]
2024-12-23 13:55 ` Eli Zaretskii
2024-12-23 14:44 ` Ship Mints
2024-12-23 15:06 ` Eli Zaretskii
2024-12-23 19:43 ` Ship Mints
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='CAN+1Hbp5MACbrKo3KTo5G0CXDo0v3kwSxes=Z3ZfJLsp-QB5Qg@mail.gmail.com' \
--to=shipmints@gmail.com \
--cc=74833@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=gerd.moellmann@gmail.com \
--cc=jared@finder.org \
--cc=rms@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 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).