From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Enabling Xterm-Mouse-Mode Date: Sun, 08 Dec 2024 08:07:51 +0200 Message-ID: <86cyi2hfm0.fsf@gnu.org> References: <87o71p2o0a.fsf@posteo.net> <86ikrxkpj2.fsf@gnu.org> <87jzcd114q.fsf@posteo.net> <3d916e84b1c0662850a90b572ccc0a91@finder.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9318"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, Emacs-devel@gnu.org To: Jared Finder Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 08 07:08:40 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tKAT7-0002GS-S8 for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Dec 2024 07:08:37 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tKASR-0000JH-4v; Sun, 08 Dec 2024 01:07:55 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tKASP-0000It-GC for Emacs-devel@gnu.org; Sun, 08 Dec 2024 01:07:53 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tKASO-0000pJ-WB; Sun, 08 Dec 2024 01:07:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=smaRXxc75ieYJrNAdk4cVWJ/SueGwkFFTdld70leHhU=; b=Qbls7YRTf1Tl VjtkOvX5WTzBH8UH4xvbs9Ec4XSeQFynu87WV9wuWp9N41TuZRZkxeB0BrQOtA5yahLjlm5PPCvz3 sPOAXXUOnUSlkXsAAgKgTlJOMes3PoZsAKSvXzxf9X9xLMgEZGHIQNudDjB0lESN3zefHUz/3+U29 LqTy7+OiFXVswh84BFAazDvH6RLljg8UXs5LMrHWcZKvOGVAi/DuiCo5dc6Ry8e5hCbYftldxcUE5 F/TYHgPuCpygpOP3anEt1e2+jhCjKGJ1smvPxPMtI//TzSyv1G7mVXsuAsy1F+NT+X52FyP9Y7TjD KrL0taxZPw8AXpvjbEVwSQ==; In-Reply-To: <3d916e84b1c0662850a90b572ccc0a91@finder.org> (message from Jared Finder on Sat, 07 Dec 2024 16:37:46 -0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:326177 Archived-At: > Date: Sat, 07 Dec 2024 16:37:46 -0800 > From: Jared Finder > Cc: Eli Zaretskii , Emacs-devel@gnu.org > > On 2024-12-06 03:50, Philip Kaludercic wrote: > > Eli Zaretskii writes: > > > >>> From: Philip Kaludercic > >>> Date: Fri, 06 Dec 2024 08:51:01 +0000 > >>> > >>> > >>> Is there a reason that we do not enable `xterm-mouse-mode' in emacs > >>> -nw > >>> by default? Are there issues with the implementation that prevent > >>> the > >>> change? > >> > >> Users might not expect that? Certain escape sequences might not > >> really be mouse-related? > > > > From observing people (often accidentally) using Emacs in my computer > > labs, they do them to expect that. Clicking to move the point is > > something that people appear to do very intuitively, and the TUI menus > > hint toward mouse-usage as well. > > > >> I've added Jared to this discussion. > > 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? > 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?