all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Kastrup <dak@gnu.org>
Cc: emacs-pretest-bug@gnu.org, Drew Adams <drew.adams@oracle.com>
Subject: Re: More key strangeness
Date: Mon, 19 May 2008 04:20:02 -0400	[thread overview]
Message-ID: <jwvy766k8t1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <85tzgwufnn.fsf_-_@lola.goethe.zz> (David Kastrup's message of "Sun, 18 May 2008 11:26:20 +0200")

> Typing C-h k C-x <menu-bar> <options> <highlight-paren-mode>
> gives the resulting error message
> C-x <menu-bar> is undefined
> in the *Messages* buffer, but
> <highlight-paren-mode> is undefined
> in the echo area.

> Wow.  Where does that discrepancy come from?

I believe there's no discrepancy: What happens is that after selecting
the menu, you end up with 4 events:

   C-x <menu-bar> <options> <highlight-paren-mode>

and when reading them to find the corresponding key-sequence and
command, the first key-sequence is

   C-x <menu-bar>

and is unbound, so it generates the message "C-x <menu-bar> is
undefined".  Then the next event probably generates "<options> is undefined",
and so does <highlight-paren-mode>.  So you should see 3 messages
in total.


        Stefan





  reply	other threads:[~2008-05-19  8:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87myj88yot.fsf@cyd.mit.edu>
2008-05-13 20:01 ` 23.0.60; kbd returns wrong value Drew Adams
2008-05-16  7:14   ` Drew Adams
2008-05-16  9:32     ` David Kastrup
2008-05-17 15:13       ` Drew Adams
2008-05-17 23:46         ` Drew Adams
2008-05-18  0:00           ` Drew Adams
2008-05-18  3:12       ` Stefan Monnier
2008-05-18  5:32         ` Drew Adams
2008-05-18  9:26           ` More key strangeness (was: 23.0.60; kbd returns wrong value) David Kastrup
2008-05-19  8:20             ` Stefan Monnier [this message]
2008-08-19 21:55   ` bug#237: marked as done (23.0.60; " Emacs bug Tracking System

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=jwvy766k8t1.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dak@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-pretest-bug@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.
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.