unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Schutte <m.schutte.jr@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Ignoring a key event completely
Date: Wed, 14 May 2008 15:03:50 +0000 (UTC)	[thread overview]
Message-ID: <20080514150346.GA8795@debian.homenet> (raw)
In-Reply-To: <g0c31g$vb5$1@ger.gmane.org>

On Tue, May 13, 2008 at 06:54:09AM -0600, Kevin Rodgers wrote:
> Does `C-h v function-key-map' show a key sequence that is mapped to
> [key-17]?

No, it doesn’t.  I also tried (define-key function-key-map [key-17] [])
now, but it seems to behave exactly the same way as doing it in
special-event-map (i.e. I have to see about C-, M-, etc. myself).  Is
there some more magic I’m missing?

-- 
Michael Schutte <m.schutte.jr@gmail.com>





      reply	other threads:[~2008-05-14 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 14:16 Ignoring a key event completely Michael Schutte
2008-05-13  2:53 ` Kevin Rodgers
2008-05-13  7:44   ` Michael Schutte
2008-05-13 12:54     ` Kevin Rodgers
2008-05-14 15:03       ` Michael Schutte [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

  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=20080514150346.GA8795@debian.homenet \
    --to=m.schutte.jr@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).