From: David Kastrup <dak@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Juri Linkov' <juri@jurta.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Key/menu bug? (was: customizing key definitions with Customize)
Date: Sun, 18 May 2008 11:07:50 +0200 [thread overview]
Message-ID: <853aogvv2x.fsf_-_@lola.goethe.zz> (raw)
In-Reply-To: <003f01c8b885$a0a3ce30$0200a8c0@us.oracle.com> (Drew Adams's message of "Sat, 17 May 2008 18:22:23 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> 4. There still is an `edmacro-parse-keys' bug that prevents some keys
> from being handled correctly. With the attached code, the only such
> key in the global map is, I think, "M-<" - see the separate bug
> report. Someone more knowledgeable will need to fix
> `edmacro-parse-keys' the right way.
I was trying to guess whether there can be something like M-<menu-bar>
or similarly contrived, so I did C-h k, held control and selected a menu
entry.
This gave me
<menu-bar> <buffer> C-@ runs the command (lambda nil (interactive)
(switch-to-buffer #<buffer *wide reply to Drew Adams*>)), which is an
interactive Lisp function.
It is bound to <menu-bar> <buffer> C-@.
(anonymous)
Not documented.
This can't be right, can it? It is on
GNU Emacs 23.0.60.13 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of
2008-05-13 on lola
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-05-18 9:07 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 19:40 customizing key definitions with Customize Drew Adams
2008-05-11 22:02 ` Lennart Borgman (gmail)
2008-05-11 22:28 ` Drew Adams
2008-05-11 22:40 ` Lennart Borgman (gmail)
2008-05-11 23:02 ` Drew Adams
2008-05-11 23:09 ` Lennart Borgman (gmail)
2008-05-11 23:19 ` Drew Adams
2008-05-11 23:23 ` Lennart Borgman (gmail)
2008-05-11 23:34 ` Drew Adams
2008-05-12 20:42 ` Lennart Borgman (gmail)
2008-05-14 5:24 ` Drew Adams
2008-05-12 8:59 ` Reiner Steib
2008-05-12 20:58 ` Drew Adams
2008-05-12 11:20 ` Richard M Stallman
2008-05-12 14:01 ` Drew Adams
2008-05-13 0:03 ` Juri Linkov
2008-05-13 0:40 ` Lennart Borgman (gmail)
2008-05-13 14:59 ` Richard M Stallman
2008-05-13 23:59 ` Juri Linkov
2008-05-14 1:10 ` Stefan Monnier
2008-05-14 16:40 ` Richard M Stallman
2008-05-15 4:46 ` Drew Adams
2008-05-15 17:39 ` Richard M Stallman
2008-05-16 8:01 ` Drew Adams
2008-05-16 17:46 ` Richard M Stallman
2008-05-16 18:00 ` David Kastrup
2008-05-16 23:58 ` Drew Adams
2008-05-17 5:00 ` Richard M Stallman
2008-05-16 7:51 ` Drew Adams
2008-05-18 1:22 ` Drew Adams
2008-05-18 9:07 ` David Kastrup [this message]
2008-05-13 15:07 ` David Reitter
2008-05-13 19:05 ` David Kastrup
2008-05-14 5:23 ` Drew Adams
2008-05-13 5:16 ` Richard M Stallman
2008-05-14 5:23 ` Drew Adams
2008-05-14 16:39 ` Richard M Stallman
2008-05-15 4:36 ` Drew Adams
2008-05-15 17:39 ` Richard M Stallman
2008-05-16 8:02 ` Drew Adams
2008-05-16 17:46 ` Richard M Stallman
2008-05-16 23:58 ` Drew Adams
2008-05-12 20:42 ` Lennart Borgman (gmail)
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=853aogvv2x.fsf_-_@lola.goethe.zz \
--to=dak@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).