unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Fri, 06 Dec 2024 11:50:29 +0000	[thread overview]
Message-ID: <87jzcd114q.fsf@posteo.net> (raw)
In-Reply-To: <86ikrxkpj2.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Dec 2024 13:40:49 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Philip Kaludercic <philipk@posteo.net>
>> 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.



  reply	other threads:[~2024-12-06 11:50 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 [this message]
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
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=87jzcd114q.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).