unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Aaron Meurer'" <asmeurer@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Mouse support does not work
Date: Sat, 14 Jan 2012 12:08:30 -0800	[thread overview]
Message-ID: <1A8CE007D6A94A659655E374A48FB597@us.oracle.com> (raw)
In-Reply-To: <CAKgW=6JtUk4PCJvJ2sRVpjX142xCyLb8MWuVHyL_y3NEB5DySQ@mail.gmail.com>

> >> > Wrt keystroke echoing, you can use `echo-keystrokes', as I
> >> > mentioned. You also have `C-h l', to see the last 100 keystrokes.
> >>
> >> echo-keystrokes only seems to work within some lisp code, which I
> >> unfortunately am not good enough with yet to do anything useful.
> >
> > I think it works always, but it is true that some commands 
> > etc. might bind it to 0 so it has no effect in some context.
> 
> Maybe I'm missing something then.  M-x echo-keystrokes doesn't work.
> How would one run this (without incorporating it into some lisp code)?

It is a user option, IOW a variable that you can customize.  It is not a
function, let alone a command (so you cannot invoke it using `M-x').

Use `C-h v echo-keystrokes' to see its doc.

However, the doc string is incomplete - see this bug report:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10503.  For more complete info, see
the Emacs or Elisp manual: use `i echo-keystrokes' in the manual.

The way to make `echo-keystrokes' take effect or not is to use `M-x
customize-option' or `M-x set-variable'.

> >> C-h l doesn't seem to show mouse events.
> >
> > It does for me:
> >
> > ... SPC <down-mouse-1> <mouse-1> C-c C-c y e s <return>
> > <help-echo> <switch-frame> <switch-frame> <down-mouse-1>
> > <mouse-movement> <mouse-movement> <drag-mouse-1> <down-mouse-3>
> > <mouse-3> <down-mouse-1> <mouse-1> <double-down-mouse-1>
> > <double-mouse-1> <down-mouse-3> <mouse-3> C-h l
> >
> > And it works whether I use a graphic display or `emacs -nw'.
> >
> 
> Actually, I think maybe it does for me too. But it shows it in the
> form of garbage that I don't know how to read:
> 
> ESC [ > 0 ; 9 5 ; c ESC x e c TAB DEL DEL ESC [ M a
> ] E ESC [ M a ] E ESC [ M a ] E ESC [ M a ] E ESC [
> M a ] E ESC [ M ` ] E ESC [ M ` ] E ESC [ M ` ] E ESC
> [ M ` ] E C-h C-g C-h C-h l ESC [ M a ] E ESC [ M a
> ] E ESC [ M a ] E ESC [ M ` ] E ESC [ M ` ] E ESC [
> M ` ] E ESC [ M ` ] E ESC [ M SPC \300\262 , ESC [
> M # \300\262 , ESC [ M SPC \300\243 ) ESC [ M # \300\243
> ) ESC [ M SPC \300\241 ' ESC [ M # \300\241 ' C-h l
> ESC [ M a \300\236 & C-h l

Those look like keyboard keys to me, not mouse events.  If you use the mouse
(e.g. click `mouse-1' somewhere, then click `mouse-3' somewhere, to select some
text) you should see mouse events such as I show above.




  reply	other threads:[~2012-01-14 20:08 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  9:18 Mouse support does not work Aaron Meurer
2012-01-10 17:24 ` Tassilo Horn
2012-01-10 18:29   ` Eli Zaretskii
2012-01-10 21:00     ` Tassilo Horn
2012-01-10 21:32       ` Peter Dyballa
2012-01-11  8:04         ` Tassilo Horn
2012-01-11 22:12           ` Peter Dyballa
2012-01-12  7:22             ` Tassilo Horn
2012-01-12  9:44               ` Peter Dyballa
2012-01-12  9:56                 ` Tassilo Horn
2012-01-12 10:06                   ` Peter Dyballa
2012-01-10 21:31     ` Peter Dyballa
2012-01-10 21:29 ` Peter Dyballa
2012-01-10 22:06   ` Aaron Meurer
2012-01-10 22:31     ` Peter Dyballa
2012-01-10 22:50       ` Aaron Meurer
2012-01-10 23:26         ` Peter Dyballa
2012-01-11 12:50           ` Aaron Meurer
2012-01-11 14:24             ` Drew Adams
2012-01-11 14:37             ` Drew Adams
2012-01-11 15:28               ` Aaron Meurer
2012-01-11 19:10                 ` Drew Adams
2012-01-11 21:14                   ` Aaron Meurer
2012-01-14 16:45                     ` Aaron Meurer
2012-01-14 16:53                       ` Drew Adams
2012-01-14 17:26                         ` Aaron Meurer
2012-01-14 17:37                           ` Drew Adams
2012-01-14 17:49                             ` Aaron Meurer
2012-01-14 18:20                               ` Drew Adams
2012-01-14 19:55                                 ` Aaron Meurer
2012-01-14 20:08                                   ` Drew Adams [this message]
2012-01-14 20:32                                     ` Aaron Meurer
2012-01-14 21:00                                       ` Drew Adams
2012-01-15  0:01                                         ` Aaron Meurer
2012-01-15  0:55                                     ` Peter Dyballa
2012-01-15  0:58                                       ` Drew Adams
2012-01-15 15:19                                         ` Peter Dyballa
2012-01-15  1:13                                       ` Aaron Meurer
2012-01-15 15:28                                         ` Peter Dyballa
2012-01-15 15:47                                           ` Aaron Meurer
2012-01-15 16:30                                             ` Peter Dyballa
2012-01-16 18:22                                               ` Aaron Meurer
2012-01-14 17:46                           ` Aaron Meurer
2012-01-10 23:44         ` Peter Dyballa
2012-01-11  6:31           ` Jonathan Groll
2012-01-11  6:15         ` Jonathan Groll

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=1A8CE007D6A94A659655E374A48FB597@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=asmeurer@gmail.com \
    --cc=help-gnu-emacs@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.
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).