all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Input events and (interactive "e")
Date: Mon, 25 Jun 2012 05:56:45 +0300	[thread overview]
Message-ID: <83txy09k0i.fsf@gnu.org> (raw)
In-Reply-To: <jwvehp4cgq1.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sun, 24 Jun 2012 21:40:54 -0400
> Cc: emacs-devel@gnu.org
> 
> >> > How about the broader question, regarding non-keyboard events and "e":
> >> > any hints and/or suggestions there?  Should I just document what I
> >> > found out and understood?
> >> IIRC, the meaning of "e" was extended so that you can have a single
> >> command that works both for mouse-clicks and for key events.
> > I rather meant events that are neither keyboard nor mouse events.
> > Like delete-frame, help-echo, etc.
> 
> AFAIK, Emacs has never made such a distinction.

I understand, but the problem is, the manual doesn't make that clear
at all.  If you read the manual, "e" is only about mouse events,
accessing non-mouse event lists is not covered (in fact, even the fact
that they are lists is barely mentioned), and binding them to keys is
described deceptively, because the text uses KEY to describe what
should have been called EVENT.



      reply	other threads:[~2012-06-25  2:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23 15:04 Input events and (interactive "e") Eli Zaretskii
2012-06-24  4:45 ` Stefan Monnier
2012-06-24 11:49   ` Juanma Barranquero
2012-06-24 16:07     ` Eli Zaretskii
2012-06-24 13:14   ` Drew Adams
2012-06-24 15:51   ` Eli Zaretskii
2012-06-24 18:57     ` Stefan Monnier
2012-06-24 19:28       ` Eli Zaretskii
2012-06-25  1:40         ` Stefan Monnier
2012-06-25  2:56           ` Eli Zaretskii [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83txy09k0i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.