From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jared Finder <jared@finder.org>, Emacs-devel@gnu.org
Subject: Re: Enabling Xterm-Mouse-Mode
Date: Thu, 12 Dec 2024 16:48:32 +0000 [thread overview]
Message-ID: <875xnou9sv.fsf@posteo.net> (raw)
In-Reply-To: <87a5d0uahq.fsf@posteo.net> (Philip Kaludercic's message of "Thu, 12 Dec 2024 17:33:37 +0100")
Philip Kaludercic <philipk@posteo.net> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Date: Mon, 09 Dec 2024 22:22:06 -0800
>>> From: Jared Finder <jared@finder.org>
>>> Cc: philipk@posteo.net, Emacs-devel@gnu.org
>>>
>>> On 2024-12-08 08:35, Jared Finder wrote:
>>> > On 2024-12-07 22:07, Eli Zaretskii wrote:
>>> >>> Date: Sat, 07 Dec 2024 16:37:46 -0800
>>> >>> From: Jared Finder <jared@finder.org>
>>> >>> Cc: Eli Zaretskii <eliz@gnu.org>, Emacs-devel@gnu.org
>>> >>>
>>> >>> As long as we can defer actually sending the mouse tracking escape
>>> >>> sequence until after init file load I think this is fine. All
>>> >>> terminals
>>> >>> I've worked with work fine with xterm-mouse-mode's defaults, but
>>> >>> since
>>> >>> there's so many different terminals I want to ensure user
>>> >>> compatibility
>>> >>> variables still work (currently just xterm-mouse-utf-8, I expect to
>>> >>> create a new one for bug #73469).
>>> >>
>>> >> So this would require some changes in the code, to make sure the
>>> >> escape sequences are delayed?
>>> >
>>> > Yes, some changes, though they are straightforward.
>>> >
>>> >>> Also, I expect this would only be done when the envvar TERM indicates
>>> >>> the user is on an xterm-compatible terminal.
>>> >>
>>> >> How do we know which ones are compatible?
>>> >
>>> > If Emacs decided to load term/xterm.el then the terminal advertised
>>> > itself as xterm compatible and I think we could enable
>>> > xterm-mouse-mode. There's no termcap entry for mouse support, sadly.
>>>
>>> Relying on term/xterm.el being loaded made the patch very
>>> straightforward because it gets loaded after user init files. Patch
>>> attached.
>>
>> Thanks, installed on the master branch.
>
> I am not sure if something else is broken on master, or if I made a
> mistake, but the patch doesn't appear to have any effect?
No, it was my mistake. It all works as intended, thanks Jared!
next prev parent reply other threads:[~2024-12-12 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 8:51 Enabling Xterm-Mouse-Mode Philip Kaludercic
2024-12-06 11:40 ` Eli Zaretskii
2024-12-06 11:50 ` Philip Kaludercic
2024-12-08 0:37 ` Jared Finder
2024-12-08 6:07 ` Eli Zaretskii
2024-12-08 16:35 ` Jared Finder
2024-12-10 6:22 ` Jared Finder
2024-12-12 10:52 ` Eli Zaretskii
2024-12-12 16:33 ` Philip Kaludercic
2024-12-12 16:48 ` Philip Kaludercic [this message]
2024-12-08 5:17 ` Richard Stallman
2024-12-08 9:55 ` Philip Kaludercic
2024-12-08 16:40 ` Jared Finder
2024-12-11 4:33 ` Richard Stallman
2024-12-11 6:27 ` Jared Finder
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=875xnou9sv.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=Emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=jared@finder.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).