From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: `xterm-mouse-mode' has a bogus Custom group
Date: Tue, 12 Apr 2005 19:01:12 -0500 (CDT) [thread overview]
Message-ID: <200504130001.j3D01Cn19635@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1DLP6r-0007EK-20@fencepost.gnu.org> (message from Richard Stallman on Tue, 12 Apr 2005 13:23:33 -0400)
I have now enabled Xterm Mouse mode by default in xterm style terminal
emulators, as requested. As I pointed out before, this is not without
problems.
One of the worst kind of problems occurs when you click on the mode
line. You get no tooltips or echo area messages to tell you what is
going to happen, because, even with Xterm Mouse mode enabled, Emacs
does not respond to mouse over. So basically, when you click on the
mode line you have no idea what is going to happen.
The main reason for wanting to click on the mode line is to resize the
window. Should we not disable all the other fireworks in the mode
line when we can not warn the user about them, that is, when not
running under a window system?
A basic problem with Xterm Mouse mode is that mouse clicks are
enabled, but the usual tools to tell you that mouse clicks are going
to do something special and what that is (mouse face and tooltips or
echo area messages) are not.
Sincerely,
Luc.
next prev parent reply other threads:[~2005-04-13 0:01 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 3:51 `xterm-mouse-mode' has a bogus Custom group Luc Teirlinck
2005-04-02 5:30 ` Nick Roberts
2005-04-02 13:46 ` Luc Teirlinck
2005-04-05 6:25 ` Nick Roberts
2005-04-06 0:00 ` Luc Teirlinck
2005-04-06 0:17 ` David Kastrup
2005-04-06 23:01 ` Richard Stallman
2005-04-06 23:22 ` David Kastrup
2005-04-07 8:44 ` Kim F. Storm
2005-04-07 9:21 ` Han Boetes
2005-04-07 9:29 ` Nick Roberts
2005-04-08 3:22 ` Richard Stallman
2005-04-07 9:30 ` David Kastrup
2005-04-08 3:22 ` Richard Stallman
2005-04-08 8:13 ` David Kastrup
2005-04-06 2:59 ` Nick Roberts
2005-04-07 0:45 ` Luc Teirlinck
2005-04-08 1:50 ` Nick Roberts
2005-04-08 1:59 ` Luc Teirlinck
2005-04-08 2:13 ` Nick Roberts
2005-04-08 15:14 ` Andreas Schwab
2005-04-08 2:22 ` Nick Roberts
2005-04-08 14:32 ` Richard Stallman
2005-04-08 16:05 ` Luc Teirlinck
2005-04-08 21:54 ` Nick Roberts
2005-04-09 0:28 ` Luc Teirlinck
2005-04-09 4:06 ` Luc Teirlinck
2005-04-09 5:22 ` Nick Roberts
2005-04-09 7:53 ` Eli Zaretskii
2005-04-09 11:04 ` Nick Roberts
2005-04-09 15:37 ` Luc Teirlinck
2005-04-09 22:21 ` Nick Roberts
2005-04-10 1:54 ` Richard Stallman
2005-04-10 1:54 ` Richard Stallman
2005-04-10 4:54 ` Eli Zaretskii
2005-04-10 13:18 ` Luc Teirlinck
2005-04-10 14:37 ` Stefan Monnier
2005-04-10 15:29 ` Luc Teirlinck
2005-04-10 21:51 ` Nick Roberts
2005-04-10 23:30 ` Luc Teirlinck
2005-04-13 5:02 ` Richard Stallman
2005-04-13 10:21 ` David Kastrup
2005-04-11 1:56 ` Richard Stallman
2005-04-12 1:04 ` Luc Teirlinck
2005-04-12 1:28 ` Luc Teirlinck
2005-04-12 17:25 ` Richard Stallman
2005-04-13 1:24 ` Luc Teirlinck
2005-04-13 4:58 ` Jan D.
2005-04-13 5:28 ` Eli Zaretskii
2005-04-14 2:16 ` Luc Teirlinck
2005-04-14 4:06 ` Eli Zaretskii
2005-04-14 7:40 ` Kim F. Storm
2005-04-15 2:04 ` Luc Teirlinck
2005-04-15 8:23 ` Miles Bader
2005-04-15 8:47 ` Ismail Donmez
2005-04-15 8:47 ` Kim F. Storm
2005-04-15 9:07 ` Eli Zaretskii
2005-04-16 1:06 ` Luc Teirlinck
2005-04-14 19:03 ` Richard Stallman
2005-04-15 2:11 ` Luc Teirlinck
2005-04-13 5:21 ` Eli Zaretskii
2005-04-12 2:12 ` Luc Teirlinck
2005-04-12 2:47 ` Luc Teirlinck
2005-04-12 17:23 ` Richard Stallman
2005-04-13 0:01 ` Luc Teirlinck [this message]
2005-04-12 23:31 ` David Kastrup
2005-04-13 1:49 ` Luc Teirlinck
2005-04-13 2:17 ` Stefan Monnier
2005-04-13 18:31 ` Richard Stallman
2005-04-10 14:27 ` Stefan Monnier
2005-04-11 1:56 ` Richard Stallman
2005-04-06 3:02 ` Richard Stallman
2005-04-06 8:22 ` David Kastrup
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=200504130001.j3D01Cn19635@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).