all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
	"'Eli Zaretskii'" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: Input events and (interactive "e")
Date: Sun, 24 Jun 2012 06:14:27 -0700	[thread overview]
Message-ID: <086B863071604BEDA51EFBAF0092C589@us.oracle.com> (raw)
In-Reply-To: <jwv62ahz5ff.fsf-monnier+emacs@gnu.org>

> Think of "C-x <someevent> C-s".  Should "someevent" be considered as
> part of the whole key-sequence for the purpose of command 
> lookup, or is "someevent" sufficiently special that it should be run
> immediately regardless of the previous "C-x" and then ignored from
> the overall key-sequence which will just read "C-x C-s"?
> If the latter, then your event should be handled by special-event-map.

1. This info was helpful to me.  I've added it to the commentary in
`thumb-frm.el', which mentions that users can substitute thumbifying for
iconifying everywhere, including, say, clicking a window-mgr minimize button.
It's good to be aware of, even if a user might never accidentally do `C-x
<click-minimize-button> C-s'.

2. I support Eli's questions about documenting `e' more generally.  No doubt
there is stuff here, too, that I and others are unaware of.




  parent reply	other threads:[~2012-06-24 13:14 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 [this message]
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

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=086B863071604BEDA51EFBAF0092C589@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=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.