Re: `xterm-mouse-mode' has a bogus Custom group

[David Kastrup]

Luc Teirlinck <address@hidden> writes:

> 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.

Tooltips are an optional help.  A lot of people make do without them.
XEmacs has no working tooltips even today.  So this is not so very
tragic.

> 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?

The "fireworks" are not destructive and usually deliver a text message
what happened.  I don't see much of a problem here.

We might want assign a mouse-button+modifier combination to explictly
providing a tooltip in the echo area: that way Xterm users can
"explore" things by clicking wildly in a similar way as mouse-over
enabled people can.  Since point-positioning is not useful on the
modeline, one could even use mouse-1 (when used undragged) for that,
reserving mouse-2 for the actual action.  That way people will tend
not to trigger something accidentally.

> 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.

I don't see much tragedy here, like I said.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum