From: Jared Finder via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, 74833@debbugs.gnu.org,
fgunbin@fastmail.fm, shipmints@gmail.com, 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: Fri, 27 Dec 2024 23:08:27 -0800 [thread overview]
Message-ID: <5e102d7d29eba618874c0b41e9815b8d@finder.org> (raw)
In-Reply-To: <865xn5y2n0.fsf@gnu.org>
On 2024-12-27 00:02, Eli Zaretskii wrote:
>> Date: Thu, 26 Dec 2024 15:51:14 -0800
>> From: Jared Finder <jared@finder.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org,
>> gerd.moellmann@gmail.com,
>> fgunbin@fastmail.fm, 74833@debbugs.gnu.org
>>
>> On 2024-12-23 11:43, Ship Mints wrote:
>> > On Mon, Dec 23, 2024 at 4:07 PM Eli Zaretskii <eliz@gnu.org> wrote:
>> >>> From: Ship Mints <shipmints@gmail.com>
>> >>>
>> >>> Away from a computer, but I think this is still the same in 0.82
>> >>> these days and I assume you're using modern
>> >>> ssh.
>> >>>
>> >>> https://serverfault.com/a/819740
>> >>
>> >> OK, so does this mean we want to tell PuTTY users to configure this in
>> >> some specific way that Emacs can recognize?
>> >
>> > Still away from a computer. If you can set a variable using that method
>> > and have it pass through for you to test in lisp, then it would be a
>> > good idea to recommend. We could suggest using TERM_PROGRAM and setting
>> > it to "Putty".
>>
>> What if we only auto-enabled xterm-mouse-mode on OSC52 compatible
>> terminals?
>
> On OSC52 compatible terminals, or on OSC52 compatible terminals that
> define TERM to xterm-like string? The latter sounds like a good idea
> to me, but only if support for OSC52 necessarily means xterm-mouse
> escape sequences must be supported. Is this conjecture indeed true?
I'm proposing Emacs have a manually curated allow list for now for
auto-enabling xterm-mouse-mode. Being OSC52 compatible gets us the copy
/ paste issue this bug mentioned. We can add other conditions going
forward.
>> Between $TERM and the results from the terminal escape
>> sequence "ESC [ > 0 q", Emacs can have high confidence if it is
>> running
>> on an OSC52 compatible terminal. I checked against most of the
>> terminals
>> mentioned at
>> https://can-i-use-terminal.github.io/features/osc52copy.html I just
>> wasn't able to test Foot (Wayland-only), hterm (Chromebook-only),
>> mintty
>> (Cygwin-only), or xterm.js (I have no idea how to test).
>
> How do I check this? can you show some script or Lisp or whatever you
> used to check?
Run the following lisp code in Emacs:
(progn
(send-string-to-terminal "\e[>0q")
(let ((str "")
chr)
(while (setq chr (xterm--read-event-for-query))
(setq str (concat str (string chr))))
str))
You should get the string "\eP>|terminal name and version\e\\". For
example, under iTerm2 I get iTerm2 3.5.10 as the terminal name and
version and under Kitty I get kitty(0.38.1).
-- MJF
next prev parent reply other threads:[~2024-12-28 7:08 UTC|newest]
Thread overview: 65+ 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
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-26 23:51 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-27 8:02 ` Eli Zaretskii
2024-12-28 7:08 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-28 8:54 ` Eli Zaretskii
2024-12-29 5:16 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 7:13 ` Eli Zaretskii
2025-01-02 7:10 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 8:10 ` Eli Zaretskii
2025-01-02 16:55 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=5e102d7d29eba618874c0b41e9815b8d@finder.org \
--to=bug-gnu-emacs@gnu.org \
--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 \
--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).